yeah! thanks

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.

Wow, Thanks JIRA Agile Team, at last we got this, Thank you so much.

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"

Rudy you can view an Epic Report in a JIRA Agile board in the Report mode.

Additionally, if you want to search on the issue link type and direction, check out the Craftware Search Linked Issues plugin.

Is there any plan for us to be able to report bugs and stories by epic in a report in JIRA? Are there any plug-ins that enable this?
This seems to be a fundamental requirement. I'm surprised this is not a priority for Atlassian.

I understand that these are different fundamental datatypes, but this is a pretty serious weakness in the generally awesome "issue view". We have multiple people bit by this issue and they all export to excel and then sort. It's a giant pain.

The lack of this functionality is causing extra work for me and my teams to get a good picture of status based on Epics. It would be great to see this functionality added in the near future.

Voting to please add this capability (whether you want to call it a bug or not...). Two of the most common fields I want to sort lists by are Epic Link and Sprint, but neither supports sorting.

Note re. previous comments, Epic Name is a field only associated with Epic type issues (i.e. it's the short name you assign to an Epic), so sorting by that doesn't really help (I tried it). In Search lists, it is the column titled "Epic Link" that we want to sort on. (Regardless of the fact that, internally, Epic Link is actually an internal field that is the ID of an issue that you get the Epic Name from to display in the list as the Epic Link... that's still what we want to sort by.)

related to sorting on all Agile-specific fields (sprint, etc.)

pobara, the Epic Name field does not seem to be populated for User Stories, so I am unable to sort on it. Am I missing something?

This seems ridiculous that every field on the issues screen is clickable and consequently sortable. What's the issue with sorting by Epic Link? Ideally, I would love to see the Epic followed by all of the issues in that epic.

Yes - Displaying the Epic Link and sorting on it should work. Can't see a reason why this is a feature and not a bug.

Hello Pierre,

I think this is not Enhancement Request but it's a Functional Bug. It's logical that we can sort on displayed information (Epics, Sprints) as we can do with different kind of fields.

Working with Epic and Sprint information when we query on Story is essential.

There is the same problem with the Sprint field--and I imagine some of the other agile fields. Revise description to include these?

Thanks pobara

Hello pobara,

This issue should be set as an Enhancement request instead of a "Not a bug - Bug".
Indeed this is not a bug, but we would like to have the possibility to ORDER BY Epic Link.
Is there a workaround in order to achieve this?

Thanks,
Pierre

Hi John,

The error is correct as the "Epic Link" field is a system link, rather than the name of an epic. I believe for your usecase you want to be sorting by "Epic Name", or by "Rank" then applying a filter on the "Epic Name" column in the Issue Navigator.