Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2121

[JIRAALIGN-2121] Program Increments Removed from Epic When Attaching Epic to a Theme

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • X-Men - VH3

      Issue Summary

      Customer has a Theme with, for example, 4, program increments - P1, P2, P3, P4 and an Epic with two different program increments - e.g. P5 and P6.

      If the user tries to update the Epic to make the Theme the parent, I get the message shown in the screenshot.

      If the user clicks Continue, the PIs on the Epic are removed.

      The user can, however, update the Epic and add P5 and P6 back to the Epic even though it is now attached to the Theme.

      Steps to Reproduce

      Preconditions: There should be a Theme that belongs to Program A and PI A, There should be orphan epic that belongs to Program A and PI B.

      1. Open Epic and select the Theme from preconditions as a parent

      Expected Results

      If assigning an Epic to a Theme that has different PIs, then the PIs on the epic should NOT be removed and instead, show warning modal that says "Would you like to continue? This Theme is assigned to a different program increment(s). Continuing will misalign these work items." If click continue, show the following message under the PI field on Epic "
      This epic's program increment(s) are misaligned from its parent Theme's assigned program increment(s)." - just like how misaligned stories show when assigned to a parent feature in a different PI
       

       Actual Results

      User receives the modal window telling the PI will be removed from the epic since the theme is assigned to another PI. If the user clicks continue, the PIs are removed, and the user has to add them back manually.

      Workaround

      Manually add the desired PIs back to the Epic.

              cgottlieb@atlassian.com Caz (Inactive)
              kbaxley Kent Baxley
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: