-
Suggestion
-
Resolution: Fixed
-
None
When conducting an advanced search you cannot sort by the 'Epic Link' field.
If an advanced search of the following occurs an error is received;
project = projext xyz AND issuetype in (Theme, Story, Epic) AND component in (q, p , r) AND fixVersion = CodeNameRelease ORDER BY "Epic Link" DESC, status ASC
Error received;
Field 'Epic Link' does not support sorting.
I have searched the support knowledge base and cannot find information on this. I would have imagined this would be a basic regular use case to allow searches for stories per Epic grouping.
- incorporates
-
JSWSERVER-8515 Epic Link on the issue navigator is not sorted base on the Epic key
-
- Closed
-
- is related to
-
- Closed
-
- Closed
- derived from
-
SW-1813 Failed to load
- mentioned in
-
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-10130] Enable sorting by "Epic Link" field
Kathleen Shafer
added a comment - +1 to that comment.
Thank you JIRA Agile!
#amazing 
Kevin Moore
added a comment - There are no words in the English language sufficient enough to express the gratitude of my team at the arrival of this great day. Songs will be sung for ages telling of the glory of JIRA Agile 6.7.0.
Kevin Moore
added a comment - There are no words in the English language sufficient enough to express the gratitude of my team at the arrival of this great day. Songs will be sung for ages telling of the glory of JIRA Agile 6.7.0. 
This Suggestion has been implemented and is available in JIRA Agile 6.7.0 which is now available.
Kind regards,
Martin
JIRA Agile
I have no knowledge about additional functionality in that version screen, but it seems prudent to re-formulate requests based on updated paradigms as they come out. 
Please post-back if Dataplane will do this for you/us.
Matt,
I tried using Confluence macros earlier to pull up the report in real time by Epic, but given the number of epics we have in our major releases, the pages never loaded and timed out.
I looked at the Arsenale Dataplane and it seems it can be used with OnDemand but its not obvious they will provide this ability to report by Epics with Script Runner. I sent them a question to get their feedback.
About 6.4, it's not clear if it will be supported. Any documentation that points to this feature to be able to sort by or group by Epic LInks?
Hi Rudy, Gotcha – I didn't get that from your previous comment.
If you're a Confluence user as well, you could embed JQL-based reports for each Epic. That doesn't scale very well, but if you only have a few Epics, it might work.
You might look at Arsenale Dataplane to see if their integration with Script Runner is at all helpful for this. They have an example in there for rolling up hours across Epics. I have no idea if this opens up other opportunties for reporting based on Epics, but I've been impressed by Arsenale's work on the plugin to date.
Additionally, I'd like to see where the JIRA 6.4 Version page re-design goes. You can see some changes in the screenshots for the EAP release here.
Matt,
The epic report is per Epic, what i need is one report for a release which can be filtered by bug or user story and grouped by Epic Link.
Issue Navigator can give me that if only we could group by or sort by "Epic Link"
yeah! thanks