Epic/Capability Process Step not updated as per the mapping when child item is moved to "In Progress"

XMLWordPrintable

    • 11
    • Severity 2 - Major
    • No
    • None

      Issue Summary

      When a child item of an Epic/Capability is moved to "In Progress", the state of the Epic/Capability is transitioned to "In Progress", but the Process Step associated with it is not transitioned per the mapping. This leaves the State and the Step out of sync, requiring manual intervention to update the Step accordingly:

      Steps to Reproduce

      1. Create a Process Step for Epics with mapping between States/Steps
      2. Create an Epic in the Program that has the Process Step
      3. Create a Feature under this Epic, plus this Feature must be synced to Jira
      4. keep both, Epic and Feature with their respectives initial states/process steps
      5. Now transition the Feature to "In Progress" in Jira, forcing the state sync goes to Jira Align
      6. Go back to the Epic and see how the state and step don't match

      Expected Results

      The Epic Process step and state should be updated accordingly their mappings after the auto-update from the child issue 

      Actual Results

      The State is updated but the Step is left behind.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

        1. epic_1.png
          epic_1.png
          303 kB
        2. epic_2.png
          epic_2.png
          210 kB

            Assignee:
            Yannick Genin
            Reporter:
            Diego Larangeira
            Votes:
            11 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: