I would like to use the JIRA Structure plugin as an easy way of viewing/creating/modifying issue links.
To be more specific, I would like to see one or more epics with a tree structure of issues underneath them.
I have tried various ways of setting up the automation, and have got very close to what I need, but there is always an unwanted side-effect. To take two examples:
Example 1: Import epics, extend with their issues, and extend the issues with their parent/child relationships
Example 2: Import issues, group by epics, extend the issues with their parent/child relationships.
Is there any way to achieve what I'm looking for?
In example 1, you are first breaking the Epic link and then creating the Parent/Child link. If your concern is that you do not have an option of putting the issue under another without creating a link then I must note that currently it is impossible, but we are working on improving how dynamic and static content interact and eventually this will be possible.
In example 2, you are removing the issue from its position dictated by JQL in inserter, grouper only arranges them under Epic, but they are still part of the original JQL. I assume that you are trying to unindent the issue here. Moving it under another story will be possible due to Parent/Child link forming and Remove Extender/Inserter duplicates filter justifying the removal from JQL results.
Please, let me know if the above explanations are sufficient.
Hi all! My name is Miles and I work on the Marketplace team. We’re looking for better ways to recommend and suggest apps that are truly crowd favorites, so of course we wanted to poll the Community. ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs