View which sprint a Feature/Epic is DONE

Chris Flynn

Is there a way using Jira Portfolio to see which sprint a Feature/Epic is completed? I can use the Scope, schedule by Sprint to see every Sprint the Feature/Epic is scheduled in, but I only want to see the Feature/Epic in the Sprint that it is done. I'm trying to replicate the SAFe Program Board in Portfolio. When is the Feature/Epic done, not date or timeline, but by Sprint.

Earl McCutcheon

Hello Chris,

The best guide I am aware of for Jira & Portfolio capabilities using SAFe can be found in the white paper that can be downloaded here:

• https://www.atlassian.com/software/jira/portfolio/scaling-agile-with-safe

The Guide notes using the Individual Sprint Reports to itemize the issues completed or not completed in a specific sprint for this metric.

But for tracking which sprint an issue was resolved in is not a limitation in Portfolio but rather comes down to a limitation in the Sprint Field and the intended use case of the field for Jira limiting its ability to sort for the last sprint an issue was in, so the functionality does not extend to Portfolio.   

The Sprint Field is a multi Select field and an issue can be included in multiple sprints and at this time does not have the ability to distinguish the last sprint the issue was in at the time it was completed and rather sorts by the first sprint the issue was included in.  We have a Feature Request to include this functionality viewable here:

• https://jira.atlassian.com/browse/JSWSERVER-12432

The Best option I could think of is still going to require a bit of manual sorting but you could leverage the ClosedSprint() JQL functions to generate reports outside of portfolio with something like:

Sprint in closedSprints() AND resolution is not EMPTY ORDER BY Sprint  DESC

This would still require some additional manual manipulation however, with a CSV export to an external spreadsheet, as the Sorting Option will arrange the issue by the first sprint an issue was included in not the last, so as an exe is an issue was in sprint 1 and moved through multiple sprints not completed and then completed in a later sprint it will still be grouped at the bottom of the sprint 1 grouping rather than the sprint it was closed in as the Sprint Field comma separates the list of issues included in the order of the sprint it was included in and sort itemizes left to right.