Issue Summary

If a user edits an issue (either with the edit button or bulk update) to update the issue type of an issue, Roadmap does not automatically disassociate the issue from existing parent issue even if it does not match the Roadmap hierarchy configuration.

Steps to Reproduce

1. Create a hierarchy such as : L1 (Level 1 issue), L2 (Level 2 issue), L3 (Epic),...
2. Create an issue with Level 1 issue type.
3. Create 2 issues with Level 2 issue type.
4. Create 2 issues with Epic issue type.
5. Access the Roadmap plan which shows the issues.
6. Move the newly created Level 2 issues as child issue of Level 1 issue.
7. Move each of newly created Epic issues as child issue of Level 2 issues.
8. Review and publish the changes from plan.
9. Open one of the Level 2 issue in an issue view.
10. Edit the issue type of the Level 2 issue to Level 1 issue.
11. Access the plan again and we will see the Level 1 issue has an Epic issue as child issue which does not follow the Roadmap hierarchy.

Screen recording: JPO-4277.webm

Expected Results

• Roadmap automatically disassociate the child issue of the parent issue if the configuration is against the Roadmap's hierarchy configuration.

Actual Results

• Child issue remains to be associated with the parent issue even though it's against the Roadmap's hierarchy configuration.

Workaround

1. Expose "Parent Link" custom field by following steps here and manually remove the invalid child issues from the parent issue.
2. Dissociate the child issue from invalid parent issue from the Roadmap plan. Users can drag and drop the issue affected the issue from the plan.