-
Bug
-
Resolution: Fixed
-
Medium
-
10.72
-
5
-
Severity 2 - Major
-
Stubborn Dragons - VH1
Issue Summary
PI is not changed to parent feature PI when the story is reassigned to another feature with unassigned PI
- Occurs if the story is reassigned from Jira to a feature(Jira Epic) with an unassigned backlog PI
- Does not occur if the story is reassigned in Align
Steps to Reproduce
- Create 2 Epics in Jira and assign stories to one of the epic
- Wait for this to sync to Align
- Once synced, set a PI to Align feature(Jira Epic) with stories. (Keep the second feature to "Unassigned Backlog" PI)
- Check the Program Room for the Align Feature. No misalign story indicated.
- In Jira, move one of the stories to the other Epic without stories (Align Features with unassigned backlog PI)
- Wait for it to Sync and check Program Room again.
Expected Results
There should be no misaligned stories because the story sprint/iteration is unassigned.
Actual Results
The reassigned story is marked as misaligned in the program room even though both PI and sprints are unassigned.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- duplicates
-
JIRAALIGN-810 [JIRAALIGN-810] PI is not nulled out when moving a story to a Parent Feature that is in the Unassigned Backlog
- Closed
- is related to
-
JIRAALIGN-2341 [JIRAALIGN-2341] User Story shouldn't retain the old PI after assigned to the new parent that doesn't have the PI set
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
ALIGNSP-4270 Loading...
-
ALIGNSP-5145 Loading...
-
ALIGNSP-9310 Loading...