Uploaded image for project: 'JS - JobScheduler'
  1. JS - JobScheduler
  2. JS-1476

If all nodes of an member of a nested job chain are skipped the order should proceed with the next job chain

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.7
    • 1.9.6, 1.10
    • None
    • None

    Description

      Current Situation
      Assuming a nested job chain with three steps. When all steps of the second job chain are skipped, the third job chain will not be executed. The order disappears. When JobScheduler will be restarted order is back.

      Desired behaviour
      When all steps of a job chain in a nested job chain are skipped the order should proceed with the next job chain and should not disappear.

      Attachments

        1. JS-1476.zip
          3 kB
        2. scheduler-2015-08-31-091130.scheduler.1.9.log
          54 kB
        3. scheduler.log
          544 kB
        4. skipped node in first nested jobchain.png
          skipped node in first nested jobchain.png
          23 kB

        Issue Links

          is related to

          Feature - A feature of the product, which has yet to be developed. JS-1394 "skip node" option in a nested job chain should work

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Known Issue

          Fix - JS-1772 JobScheduler should not crash if all nodes of a nested job chain are skipped

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Released
          relates to

          Fix - JS-864 Orders of a job chain disappear when all job chain nodes are skipped

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Released

          Activity

            People

              jz Joacim Zschimmer
              ur Uwe Risse
              Santiago Aucejo Petzoldt Santiago Aucejo Petzoldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: