Moving items in the structure will update ANY task link / parent
Our organization would like to have a possibility to move any task in structure and update issue links accordingly.
F.e. Move the subtask from one issue to another in structure - this should change the parent link for the subtask.
Move task without epic link inside the Epic - update Epic link.
Move Epic task to another random task - a popup should appear with question "choose link type".
1) in our organization we quite often are moving subtasks (with Jira's "move" feature) from one parent issue to another. Use cases are different. One example: we have user story issue "write a deliverable document to the client" and subtasks are used to break down different paragraphs in the document. And sometimes we see that some of the paragraphs should be written in another document so we move those subtasks to another issue... But this is just one example, we have a lot of use cases. :) So, this feature would be very nice to have in the structure.
2) We found how to do that. This request is not relevant anymore.
3) Ability to choose between "original link to be removed, a second link to be created" would be great!
David Niro (Customer Support, ALM Works) commented
Hello Original Poster, Arthur & Edvard,
David from the ALM Works customer support team here. Thank you for the feedback!
1) "Move the subtask from one issue to another in structure - this should change the parent link for the subtask"
This would be very interesting. Sub-tasks are treated differently than other relationships in Jira. Would you mind describing in more detail the reason you would be moving sub-tasks between tasks?
2)"Move task without epic link inside the Epic - update Epic link"
This is possible, if I understand the request correctly, and I will provide additional detail below
3)"Move Epic task to another random task - a popup should appear with question 'choose link type'"
Would you be looking for the original link to be removed, a second link to be created, or maybe the option for one or the other? Any additional feedback and context will be greatly appreciated!
You can use a JQL query (or break it up into two, and use folders) to add Epics, or Issues with no Epic links to the structure. The one Insert Generator option would look like this:
project = "testing 123" AND issuetype = Epic OR (issuetype != EPIC and "Epic Link" is EMPTY)
You will next want to add an Extend Generator to "Add issues belonging to epics"
This combination will create an initial Hierarchy of Epics and Issues with no Epic Links at your top level. Then the Epics will be extended to the issues linked to them.
The final piece here is how to create the Epic Link for the "Issues with no Epic Link".
This is done through the use of copy + drag & drop (action handling)
When moving an issue with no Epic Link to an Epic, creating the Epic Link, drag the issue while holding Ctrl (PC) or Option (Mac) and place it under (slightly to the right) the Epic. This will prompt a dialogue option asking if you would like to create the link necessary to allow this action. This also works with other Link Types.
If you have any questions about how this works, or how to get it to work, please feel free to contact our Customer Support team via email: firstname.lastname@example.org or via portal: support.almworks.com
Thank you again for your feedback! We look forward to hearing more from you!!!
Especially we need "Moving items in the structure will update * links" checkbox for "Pull in child issues using the Parent Link field from Advanced Roadmaps." extender
Edvard Obločinski commented