In-progress status and process step information don't roll up to the feature's grandparent or great-grandparent when the change is triggered by the Jira Connector

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 11.14.1
    • Component/s: Jira Connector - Sync

      Issue Summary

      When a Story or Feature is moved to "In-Progress" in Jira Align by a status change and sync from Jira, not all the item hierarchy is updated. The State/Process Step does not transition to "In Progress" for the Grandparent or great-grandparent, ... of the feature. The rollup is only up to the closest parent of the feature.

      This is inconsistent with the "In-Progress" rollup initiated from the Jira Align UI.

      Steps to Reproduce

      1. Create a Theme called 'Theme1'
      2. Create a Child 'Epic1' for 'Theme1'
      3. Create a child 'Capability1' for 'Epic1'
      4. Create a child Feature 'Feature1' for 'Capability1', plus this Feature must be synced to Jira
      5. Create a child Story 'Story1' for 'Feature1', plus this Feature must be synced to Jira
      6. Keep the 'Theme1, 'Epic1, 'Capability1, 'Feature1' and 'Story1' with their respective initial states/process steps
      7. Now transition the Story to "In Progress" in Jira, forcing the state sync to go to Jira Align
      8. Go back to the 'Theme1, 'Epic1, 'Capability1, 'Feature1' and 'Story1' and see how the state has transitioned

      Expected Results

      • 'Feature1' and 'Story1' are transitioned to the appropriate in-progress state and process step according to the state mapping and process step configuration for the Jira to Jira Align synchronisation.
      • 'Theme1, 'Epic1, 'Capability1 are transitioned to the 'in-progress' status and their mapped process step, if it is defined.

      Actual Results

      • 'Feature1' and 'Story1' are transitioned to the appropriate in-progress state and process step according to the state mapping and process step configuration for the Jira to Jira Align synchronisation.
      • 'Capability1' is transitioned to the 'in-progress' status and its mapped process step (if it is defined) according to the conditions outlined in JIRAALIGN-8439
      • 'Theme1' and 'Epic1, 'Capability1 are not transitioned to the 'in-progress' status and their mapped process step (if it is defined).

      Workaround

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

            Assignee:
            Yannick Genin
            Reporter:
            Francois Panaget (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: