I need to construct a search for issues based on linked issue details

[Phil W]

I have a support-centric project in which L3 support issues are created. When these turn out to be product issues we create a development-centric project bug issue and link it to the support issue.

I now need to be able to find all support issues in "waiting for bug fix" status that relate to development bugs that are closed.

How can I do this?

[Jack Brickey]

There are any numbe of ways to accomplish this OOTB. Here are a few ideas to consider.

• add a status to your workflow called say “Development” and place the JSD issue into that status when the link issue is added. This is precisely what I do.
• add a label “dev” or similar
• add a custom field to signify in development

all of the above will allow you to easily create filters and dashboards to monitor the development issues. The first has some added benefits so as monitoring average time in status.

[Phil W]

Hi Jack,

We already have Status "waiting for bug fix" in the support issue, and this is the status we move to as we add the link. I don't understand how your other suggestions would help me find the support issues in "waiting for bug fix" status that have a related dev issue in "closed" status. Can you explain?

Phil

[Jack Brickey]

@Phil Weighill-Smith, OOTB while you can't construct a JQL that would reach thru the linked issue to find the status of the linked issue my alternative suggestion would be as follows...

Use Automation to transition the JSD issue once the SW linked issue closes. If the status is unique, e.g. "Dev Complete" then you can easily search for these and take whatever action you wish on them.

FWIW, in my case I don't use this interim status, rather I simply automatically transition the JSD issue to Done and add a canned public comment to notify the customer. The comment added depends on the actual resolution of the dev issue, e.g. Done = we fixed it, Won't Don = we won't fix it, Cannot Reproduce =....

[Phil W]

Thanks Jack.

I'll just have to take a look see how I can do such automation in Jira Cloud with no plugins.

Phil

[Jack Brickey]

Sounds good. Let me know if you need any assistance.

[Vinu]

Hi @Phil Weighill-Smith

You can get this easily if you have scriptrunner plugin or anything else that can find linked issues. But I would recommend scriptrunner.

Please follow the below threads to see how it works. In case if you have any difficulty building the JQL, please let me know.

https://community.atlassian.com/t5/Jira-questions/Get-list-of-linked-issues-how-to/qaq-p/95753

https://community.atlassian.com/t5/Jira-questions/jira-query-issues-with-linked-issues/qaq-p/426769

https://community.atlassian.com/t5/Jira-questions/Show-list-of-linked-issues-from-a-number-of-issues/qaq-p/273189

Hope this helps!

[Phil W]

@Vinu, thanks for the suggestion. However, paying a subscription to use ScriptRunner just for something we need very occasionally isn't gonna happen. IMHO the lack of support for this in JQL is insane. This is a basic product feature gap.

[Vinu]

Hi @Phil Weighill-Smith

I would agree with you on why such a simple feature is not available with native Jira. And am in no position to know exactly why this is not in the native tool.

And what we consider easy might be a very high task from Atlassian's backlog. Some complex features have taken only weeks to be delivered, whereas several easy ones have taken decades.

However, there is a native issue function Linked Issues()that gets you linked issues. But I dont think that will any near to your requirement here.

Also if you think about other features and scripting capabilities that ScriptRunner can offer you, I would say that is a very useful investment.

Now if you definitely do not want to invest on a external plugin you have to write your own function using Atlassian dev tools

https://developer.atlassian.com/server/jira/platform/adding-a-jql-function-to-jira/

[Phil W]

@Vinu,

Thanks for your further comments. Since we use Jira Cloud I don't believe we are able to arbitrarily extend it without providing an externally addressable host somewhere on the public internet. Again, something we don't be able to do.

Phil