Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Table of Contents

Known Issue Status

Occurrence
Display known issue occurrence
StartingFromRelease1.3
 
Change Management Issue
Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1255
 

Behavior

  • Passed Test Case
    • Starting Situation
      • In a nested job chain an order is wating to be executed.
    • Action
      • Open the JOC, right click on the order and select the order state.
    • Behavior
      • The order can only be assigned to the states of the nested job chain but not to any state of a sub job chain.
  • Failed Test Case
    • Starting Situation
      • as above
    • Action
      • Open the JOC, right click on the order and select the order state, try to set the order's state to the state of a sub job chain.
    • Behavior
      • The order cannot be set to the sub job chain's state.
  • Explanation
    • A nested job chain includes other job chains as nodes, so for an order submitted to a nested job chain, the state is ideally a sub job chain.
    • In a practical scenario when job chains are organized under nested job chain, then the order's state can be set to one of the sub job chains.

Requirement

  • In a nested job chain the order's state can be assigned any state of a sub job chain.

Workaround

  • For ad hoc orders, i.e. with option "add order" from JOC, "Select an order state" option is available.  

Resolution

  • This behavior will not be fixed. As of now we don't see any real use case where permanent orders of a nested job chain need to be assigned to a specific state in a sub job chain. The workaround can easily be applied by using an ad hoc order that could be assigned any state of a sub job chain. 

...