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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
My team serves others within the organization. We log our work in features assigned to us within the epics created by other teams.
We'd like to have visibility of the epics we're contributing to. Ideally, we'd like to build a roadmap where we show the epic (created by another team), and underneath show all the children issues assigned to us.
I can filter the features assigned to us (that's easy) but not the epics that contain features assigned to us. Is there a way to do so?
welcome to the community!
if you are open to solutions from the Atlassian Marketplace, it sounds like the app that my team and I are working on - JXL for Jira - would be a great fit for your requirements.
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. With this, you should be able to build the view that you're looking for in no time.
This is how this could look in action (in this case, your team would be Arsenal FC):
Put simply, you'd pull in all relevant epics (i.e., epics that *are not* assigned to your team), and relevant stories (i.e., stories that *are* assigned to your team), enable the default issue hierarchy (that's just one click), and hide any issues that are not part of this hierarchy (that's another few clicks).
(Note that JXL can do much more than that: From bulk-editing via copy/paste, to issue grouping by any issue field(s), sum-ups, or conditional formatting.)
Any questions just let me know,
Best,
Hannes
Hello @Jimena Preciado Lopez
Welcome to the Atlassian community.
How are the features related to the Epics? Are the Features listed as child issues in the Epic or as Linked Issues?
Do you have any third party apps added to your Jira instance that extend JQL capabilities? Natively, regardless of whether the Features are child issues or linked issues, Jira doesn't have a JQL capability to get the associated Epics for a list of issues when that list of issues is itself derived from another filter, so the solution will require a third party app if you want something that can be used as a Filter.
What do you want to do with the output when you have it? It might be possible to get the information through an Automation Rule that does lookups of issues and branches on the results to get the Epics, producing a list that can be sent via email. However, Automation Rules can be created only by Project Administrators and Jira Administrators. And if the Features and Epics are in different project then it might be necessary to create a multiple project rule which can be done only by a Jira Administrator.
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.