-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 11.3.0
-
Component/s: Jira Connector - Sync
-
None
-
4
-
Severity 2 - Major
-
No
-
None
Issue Summary
When a Feature is moved to "In-Progress" in Jira Align by a status change and sync from Jira, its Parent Epic's/Capability's State/Process Step does not transition to "In Progress".
This is unique to when it is the Feature in the Parent-Child relationship which is specifically moved to "In-Progress" and not when the Feature is only transitioned to "In-Progress" due to its child Stories transition.
Steps to Reproduce
- Create an Epic
- Create a Feature under this Epic, plus this Feature must be synced to Jira
- Keep both, Epic and Feature with their respectives initial states/process steps
- Now transition the Feature to "In Progress" in Jira, forcing the state sync goes to Jira Align
- Go back to the Epic and see how the state has transitioned
Expected Results
The Epic should be transitioned to "In Progress" and if Process Steps are in use, then the corresponding mapped step would also be updated
Actual Results
The Epic remains in its initial State
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JIRAALIGN-4737 Epic/Capability Process Step not updated as per the mapping when child item is moved to "In Progress"
- Closed
- relates to
-
JIRAALIGN-8503 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
-
- Short Term Backlog
-
-
JAIAC-6010 Loading...
-
JAIAC-6030 Loading...
- causes
-
ALIGNSP-25916 Loading...
- mentioned in
-
Page Loading...
- resolves
-
ALIGNSP-27572 Loading...