Feature Request: Add a “Current Sprint” field for cleaner dashboards and reporting

Question

Description:
Right now, Jira’s Sprint field lists every sprint an issue has ever been part of. While historically accurate, it creates clutter on dashboards and reports, where the focus is almost always the active sprint. Teams want to know what’s happening now, not what happened months ago.

Request:
Introduce a system field (or configurable option on the Sprint field) that surfaces only the current active sprint [ (sprint in openSprints()) ].

Benefits:

* Sharper reporting: Dashboards, filters, and gadgets would show a clean view of the active sprint without old sprint data muddying results.

* Less admin overhead: Removes the need for custom fields, automation, or Marketplace apps just to hide past sprints.

* Immediate clarity: Stakeholders and leadership can see the sprint that matters at a glance, improving transparency and decision-making.

This change would bring Jira’s dashboards closer to the way agile teams actually work – focusing on the present sprint, not historical noise.

Danut M _StonikByte_ · Accepted Answer

Hi @RBT,

Welcome to the Atlassian Community!

I'm not sure if this is the right place to add a feature request for Jira Cloud. In order to be received by the Atlassian team, it should be reported to Atlassian. Maybe to the support portal https://support.atlassian.com/contact/#/. or to the Jira Cloud issue tracker https://jira.atlassian.com/browse/JSWCLOUD - although, at least in my case, this seems to be no longer possible.

I agree with you that the sprint field is a multi-valued field, which complicates the things a bit, but Jira reports and gadgets generally default to the most recent sprint or allow you to select the sprint. Also, JQL always allows you to filter by a specific sprint or by openSprints(), so I don't exactly understand why this is a limitation for you. Can you elaborate a bit on what you're trying to achieve or to give a more concrete use case/example?

Danut.

Prachi Bolar · Accepted Answer

Hello,

Welcome to the community :)

We understand that you would like to create a Feature request.

Please find more details on how a user can create a feature request for Atlassian products

https://community.atlassian.com/forums/Community-Announcements-articles/We-re-changing-how-we-manage-feature-suggestions/ba-p/2328033

You may follow the steps mentioned in the article

Thank You,

Prachi

Sami Linnanvuo _Screenful_ · Accepted Answer

@RBT if an add-on is an option, you can create a sprint reports for Jira using "current sprint" filter with the Analytics & Reports by Screenful.

The Current sprint report for Jira shows the status of the current sprint - what is completed or in progress, the sprint burndown, cumulative flow, and more. You can also compare the velocity across multiple sprints and how much was allocated vs completed per sprint.

The report can be scheduled to email or Slack. You can create the report from a template with just a few clicks, and it will always report the status of the currently active sprint.

The add-on is free for up to 10 users, and a 30-day free trial is available for all.

Hannes Obweger - JXL for Jira · Accepted Answer

Hi @RBT

welcome to the community!

If you're open to solutions from the Atlassian Marketplace, I think you'll like the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your work items (issues) that allows viewing, inline-editing, sorting, and filtering by all your work item fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable. It also comes with a long list of so-called smart columns that aren't natively available, including the active sprint (along with many other sprint-related smart columns).

This is how it looks in action:

(I'm using the last sprint here, but it would look the same for the active sprint.)

As you can see above, you can easily sort and filter by the active sprint, and also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

This all just works - there's no scripting or automation whatsoever required.

Any questions just let me know,

Best,

Hannes