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

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.)

Hi @aokeeffe_guidewire_com 

Jira does not natively support exporting multiple values from a field such as Sprint into a single CSV column, and you may refer to the following ticket from Atlassian:

https://jira.atlassian.com/browse/JRACLOUD-63747

However, you can try the Excel-like Bulk Issue Editor for Jira app, which lets you export multiple values in fields like Sprint into a single column.

Disclaimer: I work for the Ricksoft team that develops and maintains the Excel-like Bulk Issue Editor for Jira app

Could you share a little more about the report you're trying to create from the CSV? That will help us understand the expected output and suggest the best approach.

If your use case focuses on the current sprint, the app also provides an Active Sprint Filter, which lets you filter work items from all currently active sprints or select a specific active sprint before exporting the data.

You can find more details about the Active Sprint Filter here:
https://docs.ricksoft-inc.com/excel-like-issue-editor-for-jira-cloud/active-sprint-filter

Hope this helps!

Thank you.

Hi @aokeeffe_guidewire_com ,

Unfortunately there's no native setting for this — the Sprint field stores every sprint the issue has been in, and CSV export writes each value to its own column.

Two workarounds:

1. Spreadsheet formula. The last non-empty Sprint column is the current one. In Excel: =LOOKUP(2,1/(B2:Z2<>""),B2:Z2) — adjust B2:Z2 to cover your Sprint columns.

2. Automation rule. Create a single-line text custom field (e.g. "Current Sprint"). Add a rule: trigger Field value changed on Sprint → action Edit issue, set the field to {{issue.Sprint.last.name}}. Then export that field instead of Sprint.

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