-
Type:
Bug
-
Resolution: Fixed
-
Affects Version/s: 10.129.3
-
Component/s: Jira Connector - Process Steps
-
11
-
Severity 2 - Major
-
No
-
None
Issue Summary
When a child item of an Epic/Capability is moved to "In Progress", the state of the Epic/Capability is transitioned to "In Progress", but the Process Step associated with it is not transitioned per the mapping. This leaves the State and the Step out of sync, requiring manual intervention to update the Step accordingly:
Steps to Reproduce
- Create a Process Step for Epics with mapping between States/Steps
- Create an Epic in the Program that has the Process Step
- 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 and step don't match
Expected Results
The Epic Process step and state should be updated accordingly their mappings after the auto-update from the child issue
Actual Results
The State is updated but the Step is left behind.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JIRAALIGN-7536 State Roll-Up Does Not Occur To Parent Item When Feature Is Set To "In-Progress" From Jira
-
- Short Term Backlog
-
-
PS-164497 Loading...
- is related to
-
ALIGNSP-22848 Loading...
-
ALIGNSP-22929 Loading...
- is resolved by
-
JAIAC-5633 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
ALIGNSP-25420 Loading...
-
PS-121653 Loading...