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

[RBT]

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_]

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.