I have epic type issue called Requirements, which is linked to user need issues, which are again linked to child issues and so on..
Currently user needs are linked to Requirements epic via relates (Child) link type and user needs are linked to child issues via contains link type and so on.
I'm trying to develope a filter, which would show all issues from this epic in hierarchy (tree view) so would need help with jql or guidance for good plugin etc in order to come up with traceability type of report.
Managed to list all child issues via scriptrunner plugin, problem still is that how to show those in tree view instead of list view ... ?
Hi @Jouni Riimala ,
welcome to the Atlassian community!
Unfortunately this feature is not available on the cloud using builtin capabilities.
There are some available apps on the marketplace :
Hope this helps,
Welcome to the community !!
To visualize the tree hierarchy based on the issue links, we have created an add-on to track the progress at each level. Please try it out !!
Disclaimer: I work for RVS, the vendor for this app, and I am one of the developers in the team
I tried and it's quite ok. Few hopes to export section though.
It would be nice, if one could define headers as now those are named as Level_<int>_Key. For example those could be named in general as First level, Second level etc.
Summary field would be good with the key and truncated to certain length. By default Issue type would be good as a first column. Justification is that without using issue type field it's impossible to know what type of issue you are looking at. Additionally if it would be first column by default that would make type instantly clear.
Assuming, if I create a new custom field I can also use that field in views and later on with exports ?
Thanks for trying out the app.
Regarding #1 & #2, we will certainly implement this. I will keep you updated as soon as it is published.
Regarding #3, yes you can include custom fields in your reports and it will be exported as well. Also the report will roll up number custom fields and you can edit them too on the report screen.
Please do let me know for any other queries.
Maybe one more observation, reproduce this.
1. Create an epic.
2. Add about five child items.
3. Link one of those child item so that child created in section 2 is parent of this child.
4. Run hierarchy report and you might see that linked child item is appearing under epic and also rightfully under one child parent. Shortly you can see same id in two places which is not good.
... I confused even me, but hope that you got my point.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event