-
Bug
-
Resolution: Fixed
-
Medium
-
10.83
-
8
-
Severity 2 - Major
-
No
Issue Summary
When we move the Story from the parent Epic with the PI to the new Epic that doesn't have the PI set in Jira, the Story keeps the old PI relation in Jira Align, the respective message is displayed in the work item edit view.
Steps to Reproduce
There should be User Story in Jira that has a parent Epic with the PI set. There should also be the Epic with no PI. All items should be in sync with the Jira Align
- Open the User Story in Jira
- Move the Story to the Epic with no PI
- Wait until the items are synced
- Open the Story in Align and check if it is now in the Unassigned Backlog (inherited from the parent)
Expected Results
The Story belongs to the Unassigned Backlog based on the parent selection. No additional service messages are displayed.
Actual Results
Though the Story's parent is in the Unassigned backlog, there is a service message that informs users that old PI relation is retained.
Workaround
To clean up the old PI relation the story should be unassigned from the parent, the old PI should be removed, and then it can be assigned back to the parent.
- relates to
-
JIRAALIGN-810 [JIRAALIGN-810] PI is not nulled out when moving a story to a Parent Feature that is in the Unassigned Backlog
- Closed
-
JIRAALIGN-1714 [JIRAALIGN-1714] Program Room Story: Stories are marked as misaligned even with unassigned PI and Sprints/Iteration
- Closed
- is related to
-
ALIGNSP-9065 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
ALIGNSP-7035 Loading...
-
ALIGNSP-8126 Loading...
-
ALIGNSP-9310 Loading...