New Navigation, Active Sprint Name missing

[Mason W_ Foley]

Is there a toggle to enable the display of the sprint name if you only have one active sprint selected?  The new navigation doesn't show the currently selected Sprint which is less than ideal.  Please advise.

[Walter Buggenhout]

Hi @Mason W_ Foley,

It is definitely not as prominent as it used to be. It is not entirely missing, though. You can find current sprint details by clicking on the Agile icon next to the complete sprint button to get that information:

 

Hope this helps!

[Mason W_ Foley]

Compared to where it used to be, it doesn't make sense to remove it given all that real estate.  I really hope this is reconsidered.  

You can also float the mouse on the browser tab but this feels more like an oversight than an intentional improvement.

[Mason W_ Foley]

Additionally, your suggestion doesn't quite work either since all active sprints are shown...not just the one loaded.

[Abdallah Khaled]

Hi @Mason W_ Foley, Thanks for your question on the community. 

This is indeed considered in this feature request: https://jira.atlassian.com/browse/JRACLOUD-94236, I'd encourage you to add yourself as a watcher to be kept informed as to the state of the suggestion moving forward. Once the ticket is updated by our development team, you'll be notified via email.

[Bill Sheboy]

Greetings,

This seems to be a regression defect due to the design processes used, and likely not submitted as a "feature request" / suggestion.

Kind regards,
Bill

[Lou Reisch]

I agree. This definitely looks like a regression. Anyone looking at the board should be able to see what the active sprint is for that board without having to hover or click anything.

[Justin McCamish]

Please re-classify this as a regression. Literally no-one I work with who uses Jira (multiple scrummasters serving hundreds of developers) thinks it makes sense to obscure the title of the current Sprint in the board view. Fun or functional names for sprints are a frequent rallying point for agile teams. My team has been using Jira since 2010 and of all the recent (and largely positive) changes, this is one sticks out as needlessly jarring.