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
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
Hi, I need to filter the bugs which are linked with multiple tasks/story of multiple projects.
For eg: 1 story in Project A is created (Say Story 1), now there are multiple modules/projects in which tasks are created with are linked with (Story 1) and now the bugs are liked with these tasks.
Story 1 -> Task 1 -> Bug1 / Bug 2 / Bug 3
Story 1-> Task 2 -> Bug 4 / Bug 5 / Bug 6
Now I need to filter Bug 1-6 which are linked. linkedissues function won't work as it accepts only single parameter.
Hello @Priyanka Madaan
Can you provide more information for your scenario?
I understand that you want to get the Bug issues in your results, but I'm not clear on the criteria you are trying to use.
Is this what you are trying to do?
"for Story 1, get all the Bug type issues that are linked to Task type issues that are linked to Story 1"
Do you have or are you open to obtaining third party apps that extend the capabilities of Jira searching?
I also need advice regarding this topic. Could you help me out? I'm trying to retrieve all the Bug-type issues linked to Task-type issues, which are, in turn, linked to Story 1, just like Priyanka Madaan.
Thank you so much!
Hello @Chi Le
Welcome to the Atlassian community.
For future reference, when you respond on an existing post only the other responders, author, and watchers of that post see your question. Rather than adding your question to an old post (or one that already has an Accepted Answer) it is better to start a new Question to get more visibility. If your question relates to an old post, include a link to the old post for reference.
What you want is not possible with native Jira JQL functionality. Are you willing to consider getting a third party app to achieve your requirement?