-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Jira Connector - Sync
-
None
-
6
Enhancement Statement
Removing the parent epic and the assigned sprint from a Jira story (resulting in the story being in the Jira backlog) will remove the parent feature and sprint from the story in Jira Align, however the Program Increment is not removed from the story
The request is to include the ability for the Program Increment set in the JA Story to be removed when the Jira Story no longer has a sprint or parent Epic linked to it in Jira
Further Details
When a new Jira story is assigned to a Sprint and linked to a new parent Epic, and this Epic is itself linked to a Jira Fix Version , then without any user action in JA (but depending on connector sync settings), the Jira Align story can automatically:
- be set as a child of the Feature created from the Epic
- be assigned to the sprint mapped through the connector
- be linked to the Program Increment of the Feature (and the Program Increment of the Feature will have been automatically set by the Fix Version/Release Vehicle relationship)
However if the Jira story is then returned to the general backlog (no sprint assigned) and has the parent Epic removed, then synchronization to Jira Align only clears the sprint and the parent feature, the Program Increment is not removed.
As the 3 values were set by synchronization from Jira, it should be possible for a sync to unset all 3 values based on further actions taken only in Jira. Leaving the story linked to the Program Increment may result in the story affecting the results in some screens and reports. However as the Jira Story is only directly aware of 2 of the 3 values, only those 2 values (Sprint and parent Epic/Feature) can be removed from Jira Align by taking actions in a Jira Story.
- causes
-
PS-185722 Loading...
- is related to
-
ALIGNSP-27376 Loading...
-
ALIGNSP-29550 Loading...