Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Show sprint name on top of active sprint board and ordering of sprints in dropdown

J B
Contributor
June 9, 2026

Hello, 

Is it possible to show the active sprint name on top of the board Active Sprint? It is nowhere show on this board I think. E.g. when creating a new ticket, you first need to find what sprint we are on currently, in order to assign it to the next... 

sprintname.png

Another question, but related. How to I order the sprints in the dropdown? This is on a existing ticket. Now they are sort of random:

sprintoder.png

 

1 answer

1 accepted

3 votes
Answer accepted
Germán Morales _ Hiera
Atlassian Partner
June 9, 2026

Hi @J B, taking the two in turn.

On the sprint name: that's a known change in the new Jira navigation. The sprint name was pulled off the board header and there's no setting to put it back. It isn't fully gone though, click the Sprint details button (the agile icon) just to the left of Complete sprint and you'll get the sprint name, goal and dates. Plenty of people want it back on the header, so it's worth adding your vote to the open request at JRACLOUD-93338.

On the dropdown order: it isn't random, it just isn't sorted by name, number or date. Jira orders sprints by an internal algorithm based on each sprint's ID and its sequence position on the board, which is why they don't come out in numeric order. There's no option to change that sort, and it's a long-standing limitation. The only real levers are that sprint IDs follow creation order and the sequence follows where sprints sit on the board backlog, so creating them in order and reordering them on the backlog is about as close as you'll get. Atlassian documents the exact algorithm here: Sprint ordering in dropdown lists and the backlog

J B
Contributor
June 9, 2026

Thanks. Bummer they removed the name on the board, but good to see I'm not the only one requesting this. I do not want to sound too skeptical, but I've encountered similar things like this, somebody requesting changes/bugfixes etc. They usually don't get fixed in the near future. This one is created on feb 2025....

The sorting thing seems logical, but I've created these sprints in the corresponding order. 68, 69, 70, 71 etc. Now they moved all 70's before the 60's... Anyway, this is a minor thing. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events