Ultimately, what I am trying to achieve is to get all Child jiras within Epics that have the same linked issue.
I have 5 Epics that are all linked to IDEA-15 (IDEA-15 depends on them all). I want all the child jiras within those 5 Epics.
This JQL gives me the 5 Epics
>> issue in linkedIssues("IDEA-15")
I've tried both of these
>> parentEpic in (issue in linkedIssues("IDEA-15"))
>> parentEpic in (issue in linkedIssues("IDEA-15"))
Both return: Error in the JQL Query: Expecting ',' or ')' but got 'in'. (line 1, character 22)
The strange this is I dont even think the parentEpic function is working as per the help documentation here Advanced search reference - JQL functions | Jira Service Management Cloud | Atlassian Support as this search just returns the Epic itself and not the children
>> parentEpic in ("MIBR-254")
Please can you help?
Hi @Jennifer Davidson ,
There is no JQL solution for your problem without using any Marketplace Apps.
You can consider installing a Marketplace App that provides advanced JQL functions. Simply search the marketplace for 'JQL' and you'll find a bunch: https://marketplace.atlassian.com/search?query=jql
For example, with ScriptRunner you would be able to use a combination of issuesInEpics with linkedIssuesOf to solve your problem.
Without any Marketplace Apps, you will have to go for a workaround. Since there is no issue attribute that you can search for at the moment to find your issues, you will have to generate the needed attributes via a work-around.
A work around might be to use an Automation Rule to set some attribute that you can search for. For example:
Once that rule is active, these labels will start populating as you go about. And you can start searching on Labels = LinkedIssueOfIDEA-15.
You could do a one-time Bulk change on some Epics to apply these labels in bulk so that the second rule is fired and will copy down the labels for you.
just to add to Rik's answer, if you're open to solutions from the Atlassian Marketplace, another option would be to look into the more hierarchy-focused apps. These apps typically have their own, more powerful ways to sort out parent/child relationships, and therefore give you more freedom in navigating through issue hierarchies.
I can only speak for the app that my team is working on - JXL for Jira - but here, your use case should be easy to solve:
Happy to elaborate on the exact steps - but as you can see, it's really just a number of clicks. Once you got your set of issues, you can work on them directly in the app, trigger various operations in Jira, or export them for further processing.
As noted above, there's actually a number of apps that might solve your problems - by extending JQL, or by making it easier to work with issue hierarchies. You may already know that you can trial any app for free for 1 month, and depending on the size of your site, an app may be free forever; so if an app is an option for you, perhaps try out a few and see which one works best for you.
Hope this helps,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Jennifer Davidson Welcome to Atlassian Community
I think you are refferencing the Epic wrongly.
Please try
"Epic Link" in linkedIssues("PROJ-12")
Let me know if it works for you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply.
Sadly, this doesnt return anything
"Epic Link" in linkedIssues("IDEA-15")
I think Epik Link doesnt work for me since when I use it simply it doesnt return anything >>> "Epic Link" in ("MIBR-243")
No jiras returned however there are 16 jiras in this Epic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.