You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to create a view of issues where the rows returned are grouped like this:
--------------------------------------------------------------
ISSUE TYPE - - KEY - - SUMMARY
--------------------------------------------------------------
Story - - S1...
Task - - S1-T1 (where this task is issue linked to Story S1)...
Task - - S1-T2 (where this task is issue linked to Story S1)...
Task - - S1-T3 (where this task is issue linked to Story S1)...
Story - - S2...
Task - - S2-T1 (where this task is issue linked to Story S2)...
Task - - S2-T2 (where this task is issue linked to Story S2)...
Task - - S2-T3 (where this task is issue linked to Story S2)...
Is there a way to do this? How would I structure my JQL?
Thank you :-)
Hello @Deryl Coe
Welcome to the Atlassian community.
The grouping that you are attempting is not available with native Jira functionality.
It might be possible with a third party app/plug-in. Are you will to consider that? If so, are you using Jira Server, Jira Data Center, or Jira Cloud?
Hi @Deryl Coe
welcome to the community!
If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies. These issue hierarchies can be based on Jira's built-in parent/child relationships (like e.g. epic/story or story/sub-task), and/or based on issue links of configurable issue link types.
This is how it looks in action:
This all plays well with JXL's many other capabilities, such as issue grouping by any issue field(s), sum-ups, or conditional formatting.
Any questions just let me know,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.