Need ability to report on 'Current Sprint' (in a single Sprint column) when exporting to CSV

Question

We need ability to report on 'Current Sprint' (in a single Sprint column) when exporting to CSV. Currently if a Jira issue is moved from one sprint to another, the more sprints it gets pushed through, the more columns I end up having when exporting my filter view to e.g. CSV, and I first need to cleanup a number of columns to see that one currentsprint an issue is in...This is not user friendly and causes our reporting to be skewed and taking a lot of time to fix.

Is there anyway Customers come around this issue?

Thank you for help!

Aron Gombas _Midori_ · Answer

The Better Excel Exporter exports only the current sprint in the "Sprint" field, requiring no after-work. See column "N" here:

Even if it not 100% what you look for, the behavior and format of each field can be customized through the "field-helper.groovy" script with minimal effort. Also, you can ask our support team, happy to help!

(This paid and supported app is developed by our team. Free for 10 users.)

Ivan Manolov _Appfire_ · Answer

Following up on my earlier answer, @aokeeffe_guidewire_com: if you'd rather skip the custom field and automation entirely, and you're open to using an app from the Atlassian Marketplace, JXL for Jira can help with this. Specifically, its sprint smart columns allow you to get exactly one sprint value per row, no cleanup:

* An "Active sprint" column shows the sprint an item is currently in
* A "Last sprint" column covers items whose sprint has already closed
* Exporting the sheet to Excel or CSV keeps them as single columns, and a "Number of sprints" column is a nice bonus for spotting spillover

Here's the Last sprint column in action:

Disclosure: I work for the team that builds JXL.

Thanks,

Ivan

Ivan Manolov _Appfire_ · Answer

Hi @aokeeffe_guidewire_com,

The automation route @Habib__Plugio__ described is the most sustainable native fix. A few practical additions if you go that way:

* Backfill existing issues. The rule only fires on future sprint changes, so your current issues would export with an empty "Current Sprint" field. To fill them once, run a one-off scheduled rule with a JQL scope (for example your reporting filter) that performs the same edit, then disable it.
* Know what .last means. {{issue.Sprint.last.name}} writes the most recently added sprint. For items that finished in a completed sprint, that closed sprint stays in the field, which is usually what you want for reporting.
* Scope the export. If your report only concerns work currently in active sprints, adding sprint in openSprints() to the filter keeps rows without a current sprint out of the export entirely.

The underlying behavior is a long-standing limitation (the Sprint field keeps its full history and the exporter writes one column per value), so a stored single-value field is the cleanest native workaround.

Hope that helps,

Ivan