Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- If all nodes of a job chain are marked as skipped then the orders of the job chain dissapear in JOC.
- It has no effect if one of the nodes is set to be unskipped again - the orders are still not available.
Desired Behavior
- Orders disappear from a job chain if no active (unskipped) job node is present.
- This behavior applies to orders for which the initial state is the first state of a job chain.
- For orders with an initial state that is different from the first state of a job chain this behavior applies if the range of job nodes is skipped that the order is configured to be executed for.
- If at least one node in a job chain is active (not skipped) or becomes active (is being unskipped) that is in the range of the job nodes that the order is configured for then the order becomes visible.
Attachments
Issue Links
- is duplicated by
-
JS-705 Incomprehensible error message when an order is started and all job chain nodes are skipped
- Released
-
JS-464 (Permanent) Order disappears when all states of a job chain are skipped
- Closed
- is related to
-
JS-607 If the first node of a job chain is removed, all enqueued orders disappear
- Released
-
JS-1476 If all nodes of an member of a nested job chain are skipped the order should proceed with the next job chain
- Released
-
JS-1772 JobScheduler should not crash if all nodes of a nested job chain are skipped
- Released
- is required by
-
JITL-140 Provide a set of jobs to manage the critical path for job processing
- Released