Link issues in a hierarchy as you move issues around in the Structure view
Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.
This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.
Zhenya
shared this idea
Waiting for response
-
Is there still interest in this idea?
Thanks
Igor -
Zhenya, thanks for your feedback.
Structure is intentionally separated from sub-tasks, so there are no hard rules for sub-tasks and their positions in a structure.
There's "Subtasks" synchronizer and "GreenHopper" synchronizer that can be installed onto a structure and they try to maintain certain conditions, like "a sub-task should always be located under its parent JIRA-wise". If you install that synchronizer and try to move a subtask outside of its parent, it will immediately jump back. To move it to another parent you'll need to use JIRA's "move subtask" feature (and then it will be automatically moved in the structure).
More about synchronization: http://wiki.almworks.com/display/structure/Synchronization
Please indicate whether the existing functionality solves the problem, and can you suggest an improvement to make this easier for you.
Thanks!
Igor