If an Order ends in a node with a name that contains "success" then the Order is considered successful even if the final Job in the Job Chain had an error

Current Situation

• With a configuration such as

  <job_chain>
    <job_chain_node job="jobExit2" next_state="success" error_state="error" state="start">
      <on_return_codes>
        <on_return_code return_code="1..4">
          <to_state state="success"/>
        </on_return_code>
      </on_return_codes>
    </job_chain_node>
    <job_chain_node state="success"/>
    <job_chain_node state="error"/>
  </job_chain>
  

  you can provide that an Order doesn't move to the error state for some exit codes unequal 0.

• Even if the Order ends in the "success" end node unfortunately in the history it is displayed being "failed".

Desired Behavior

• An Order should be displayed being successful if it ends in a node with a name that contains "success".

Maintainer Note

• An Order doesn't really have a "success" or "failed" state.
• An Order is normally declared as being "failed" if the last Job of the Job Chain completes with a return code != 0
• Only a naming convention can solve this and determine if the final state of order signals success or failure.