Start and end date visibility on active sprint board missing

[Ademola Oladele]

I manage 2 scrum teams, one of the teams scrum board the active sprint start and end dates is always visible on the sprint board while for the other team it is not visible. How do one make the sprint start and end dates visible on a current sprint board in Jira. I have check the both boards configuration-card layout tab and nothings seems off. The board that displays the sprint start and end dates has only the “Label” filter on in the Active sprint tab, while the board that does not display the start and end dates has due date, story point and Labels filter on. So does one have to remove 2 filters and replace them with start and end dates option. Thanks 

[Bill Sheboy]

Hi @Ademola Oladele -- Welcome to the Atlassian Community!

Have you checked if the names of the sprint is where the dates are showing, and so one team's sprint names include the dates and the other does not?

Kind regards,
Bill

[Ademola Oladele]

Thank you I figured it out, it's in the sprint name. One of the boards had the sprint name and no which I changed upon closing and starting a new sprint. Jira should just allow more characters within the sprint name tab. It's always good to display the date so it's visible to everyone during stand-up and anytime they need to show the board. Thank you

[Bonnie Barron]

Our sprint name isn't showing either on our active sprint page. It shows in the backlog but our board just shows 'Core board' instead of Core Sprint 18 ([from date] - [to date]. It's not clear to me why this is. 

[Bill Sheboy]

Hi @Bonnie Barron 

There was an active incident today where the Sprint field was not displaying correctly, and it has since been resolved: 

https://jira-software.status.atlassian.com/incidents/twcldb43nbzd

Is the issue still happening for you?  If so, I recommend working with your Site Admin to submit a defect to Atlassian Support to take a look:

https://support.atlassian.com/contact/#/

Kind regards,
Bill

[Bonnie Barron]

Thanks @Bill Sheboy for the info, but our issue isn't resolved. I'll get with our Admin.