We link issues to Epic in Jira.
2 ways to add a bug in epic
1) From a bug – click 'More' => click link and select "Related to" and type in the epic number.
Now the issues will be related to the epic.
To get a list of linked issues
issue in linkedIssues("ABC-
) – works.
2) From bug screen click "Edit" and add epic link.
When we do that the bug is seen "issues in this epic" section.
How to get a list of the the "Issues in this epic" with their key and current status.?
hi @vaishali saraf ,
Epic link is majorly used to link a story .
Query can be like this for a story:
issuefunction in linkedIssuesOf("project = ABC", "is Epic of")
For 'Relate' issue link , the outward and inward description is same 'Relates to' by default.
If you want them to be separately defined , edit the description under issues tab with admin rights.
Once you have new links towards the epics from bug, use the same query 'issuelinks'.
Hope this helps.
Thanks for your answer .
issuefunction in linkedIssuesOf("project =RDPROG" , "is Epic of")
When I tried above query... I got
"Field 'issuefunction' does not exist or you do not have permission to view it."
Sorry... I am struggling here a bit.
One this is not clear ...Where should I give the number of epic ( Issue key) whose issues I want to display.
So its been a few months since my company broke down and bought script runner. I will say this. It's a fantastic plugin and does a million and one things. The big stinky though is that we have to shell out a small fortune for this added functionality that really would be awesome if it was part and parcel to the Atlassian tool set. After getting my head around groovy and the API it's fairly stunning as to what can be accomplished. If you haven't bought it and have a few plugin's on a list of items to buy but are confused as to which ones should be priority... Script Runner should be at the top of your list.
I get that scriptrunner is great and all, but if Jira is supposed to be about supporting Agile processes (which are supposed to be focused on user needs), that functionality should be built in. It's a little ironic that users everywhere on these forums ask for the capability to query hierarchies of issues from epics through stories and tasks, and the answer for years continues to be 'go buy a separate plugin'.
I've only been using Jira for 3 months, and I have already identified 6 key features of project tracking, this one included, that I don't have access to without a paid plugin (if it's available at all). I don't have the luxury of funding all those plugins, let alone waiting for the internal review and approval processes to go through for each one so that I can start tracking my work. A true user-centered product design would incorporate that kind of constraint into the product structuring and pricing so that customers aren't left high and dry without important capabilities during implementation.
Seriously - this violates everything that Jira is supposed to be about supporting.
I have a query to derive the Epics in which I want the linked issues. Is there a way to list the linked issues within the query that derives my Epics? I'd like to do this with just one query. seems I should be able to. I do not yet have script runner. I tried linkedIssuesOf() but keep getting operator errors. Like you the query derives the Epics.
Yes, essentially the first parameter can be any JQL expression, however be careful of putting complex JQL because it may affect the performance.
It is worth noting that this is a ScriptRunner function.
We don't have Scriptrunner or any other add-in to help with JQL. I'm using Jira Cloud (no version # specified in the About dialog), and this is what worked for me today in the Advanced Search JQL builder bar:
project = XYZ AND issue in linkedIssues("XZY-123") ORDER BY priority DESC, updated DESC
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events