Any assistance here would be appreciated. I am trying to publish a report in Confluence using a Jira filter. The report needs the following format. All the Epics are in one Initiative. I am able to get all the tickets using "Issuekey in childIssuesOf(InitiativeKey) "but not able to order as shown below. If you have a suggestion, please let me know:
Ticket Status Status Notes
Epic 1 In-Dev Multiline text
Story 1 from Epic 1 In-Dev Multiline text
Story 2 from Epic 1 In-Dev Multiline text
Epic 2 In-Dev Multiline text
Story 1 from Epic 2 In-Dev Multiline text
Story 2 from Epic 2 In-Dev Multiline text
Natively, I'm not sure this is possible.
You can order by Epic Link - but this will just order all the story-level issues based on Epic Link, as opposed to each Epic with a list of stories below them.
There is a workaround, if you are using a Classic Project...
Option 1 - Epic Issue Key
This workaround utilises a unique identifier common to each Epic and its children. It creates a UID at an Epic-level and then copies it to the Epic's children using Automation Rules.
The unique identifier can be used to order JQL results, and then a field unique to the Epic (Epic Name) is used to sub-order the issues with the Epic at the top.
Automation - Rule 1:
Automation - Rule 2:
Once the above is complete, use JQL such as this:
issue in portfolioChildIssuesOf("ABC-1") ORDER BY cf ASC, "Epic Name"
This is how the JQL works:
If you're not using Advanced Roadmaps - and instead linking Epics to an Initiative via Linked Issues, you could make this JQL work - for example:
"Epic Link" in linkedIssues("ABC-1","relates to") OR issue in linkedIssues("ABC-1","relates to") AND issuetype = Epic ORDER BY cf, "Epic Name"
^ If using Linked Issues, I would advise creating a unique link type for relating Epics to Initiatives, eg. Parent Of/Child Of, and replacing "relates to" above. You can have no link type in there - but this limits the use of Linked Issues for other purposes.
Option 2 - Custom Order
The above workaround utilises the Epic's Issue Key - this would put the Epics (and their children) in a sequential order - either Newest > Oldest, or Oldest > Newest depending if you use ASC or DESC.
You could have a more custom order by either:
This is how Rank might work...
^ Note: The reason branches are needed in this rule is because unlike Issue Key, Rank will change at an Epic level fluidly (Branch 1) and issues will be added to or moved between different Epics (Branch 2).
This should fulfil the need - a few notes:
There is a lot to digest above - let me know if you have any queries, or if you give one of the two options a go and need help!
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
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