+1I have a dynamic table showing me a set of filtered Jira tickets. While I’m aware I can group tickets by Parent, by selecting “Set row to Parent”, I would now like to group tickets by Initiative.
The ticket hierarchy I use is Initiative > Epic > Task. So I would like the ‘Initiative’ row grouping to show all related Epics and Tasks in the same row.
Thank you.
Best answer by alison cheney
Hi
Thank you for your response and for that extra context! You’ve definitely hit on a tricky spot with how Jira data works! Since Initiatives usually aren't tied to a specific Sprint, they end up getting filtered out of your results. This leaves the Epics and Tasks kind of floating without their Parent Initiative in that specific table view.
In the meantime, if you need to visualize this for a presentation, some users find success by:
Bringing the Initiatives onto the canvas as standard Jira Cards.
Using Lines to show the relationship to the Dynamic Table.
It’s not as automated as a single table, but it keeps that hierarchical context visible.
We would love to hear your feedback and more specific details for your use case in our Product Feedback section of the Community! Thanks again for being an active part of the community!
+24Hi
You currently cannot group Jira issues by Initiative in a Dynamic Table, grouping is limited to the Parent field and a small set of supported fields like assignee, status, priority, and issue type
Dynamic Tables let you pivot data by choosing which Jira field controls rows and columns, but only from a restricted list of fields
To learn more - Dynamic Tables - Add Jira fields to rows and columns | Community
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
+4Hi
Thank you for posting in the Lucid Community!
I wanted to jump in and add a potential workaround! While there is no specific way to group your Jira cards in Lucid by “Initiative”, there is “Work Item Type” (see image below) which is what many users utilize to organize their cards by “Initiative.” You can also create a Custom row or column if you would like to type the exact word “Initiative” on your Dynamic table.
We’re very interested in your feedback and committed to continually improving our products. If you would like to share your feedback on this specific feature, please first search the Product Feedback section of this community (with the filter Topic Type = Idea) to see if it’s already been submitted. If so, please add any additional details you’d like and upvote the request - this consolidation helps to refine feedback and properly capture the popularity of the request. If no one has submitted this idea yet, please create one of your own and be sure to include details about your use case or what you’d like to see in this experience. This will also allow other users with similar requests to discover and upvote it, then add details of their own.
Finally, for more information on how Lucid manages feedback via this community, take a look at this post:
Thanks for your feedback!
+1Thanks
I did try the Work Item Type option, but in this instance the Initiatives don’t show up because the table is also filtered by a specific Sprint. Even if they did show, the layout would not group the Epics and Tasks by Initiative, which is what I’m after.
I now realise my use case is quite niche - I want a table that summarises the filtered results by their hierarchical Initiative, while also narrowing the view to the current Sprint (which the Initiatives will not be part of per se). I’ll check out the product feedback section, thanks for sharing!
+4Hi
Thank you for your response and for that extra context! You’ve definitely hit on a tricky spot with how Jira data works! Since Initiatives usually aren't tied to a specific Sprint, they end up getting filtered out of your results. This leaves the Epics and Tasks kind of floating without their Parent Initiative in that specific table view.
In the meantime, if you need to visualize this for a presentation, some users find success by:
Bringing the Initiatives onto the canvas as standard Jira Cards.
Using Lines to show the relationship to the Dynamic Table.
It’s not as automated as a single table, but it keeps that hierarchical context visible.
We would love to hear your feedback and more specific details for your use case in our Product Feedback section of the Community! Thanks again for being an active part of the community!
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Your privacy choices
