-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 10.0.0, 10.3.12, 10.5.1, 11.3.2
-
Component/s: (Advanced Roadmaps) Plan - Dependencies
-
10
-
Severity 2 - Major
Issue Summary
Drag-dropping an issue within the 'issues without parent' section of a Jira Plan, unexpectedly sets the Parent Link for that issue.
Steps to Reproduce
- Create two Epics, Epic 1 and Epic 2, both linked to Initiative 1 as their parent.
-
- Note: Initiative 1 is in a different project and does not qualify to appear in the current plan.
- In the plan, both Epic 1 and Epic 2 appear under “Issues without parent”, since their parent (Initiative 1) is not included in that plan.
- Drag and drop Epic 3 into the plan between Epic 1 and Epic 2.
- When reviewing the changes, the Parent link for Epic 3 is automatically updated to match the parent of Epic 1 (Initiative 1).
- If you drag and drop Epic 3 below Epic 2 instead, the Parent link is updated to match Epic 2’s parent (Initiative 1).
- Based on how Advanced Roadmaps is expected to behave, this automatic change to the Parent link when simply repositioning Epics in the “Issues without parent” section does not seem correct.
Testing Epic Creation and Parent Link Updates in Kanban Board
Expected Results
The "Parent link" should not be updated by re-ranking Epics.
Actual Results
The "Parent link" is unexpectedly updated.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- links to