Issue Summary

Removing/changing a Level from the Advanced Roadmaps Hierarchy and then adding it back does not reflect on the plan without manual intervention.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Spin up a vanilla JSW instance
2. Create two projects using sample data (e.g. one Scrum and one Kanban)
3. Create a plan using these two projects as the source
4. Create an Epic on each of the projects
5. Go back to the plan, and move some existing issues under those Epics
6. Create two new standard issue types (e.g. Initiative and Theme), and add those to both projects' issue scheme
7. Create one new issue for each type, under each project
8. Edit the Advanced Roadmaps Hierarchy, adding two new levels, like below:
   1. Theme
   2. Initiative
   3. Epic
   4. Story ("All other standard issue types")
   5. Sub-task ("All sub-task issue types")
9. Go back to the plan and change the Hierarchy view to display all levels (from Theme to Sub-task)
10. Move some issues from the "issues without parent", to create the parent relationship between the issues, following the hierarchy "Theme > Initiative > Epic > Story > Sub-task"
11. Edit the hierarchy again, removing the Initiative level, and adding the Initiative issue type to the Epic level
12. Go back to the plan, and note that the Epics were moved to the "Issues without parent" section
13. Move one of the Epics to under the Theme issue type (leave the second Epic under the "issues without parent" section)
14. Add the Initiative level back to the hierarchy
15. Go back to the plan and note that the Epic issue moved previously is still under the Theme issue, while the other one was automatically moved under the Initiative.

Expected Results

Advanced Roadmaps should either, move the issue back to the "issues without parent" section, move it under the correct parent as per the Hierarchy, or at least display a "Warning" icon advising the user that the issue is not respecting the current hierarchy.

Actual Results

Not even a warning is displayed, and the issue will remain under the wrong parent (as per the hierarchy) until it is manually moved to the "issues without a parent" and then later moved back under the correct parent.

Workaround

Manually move the issue to the "issues without a parent" section and then move back under the correct parent.