Has anyone experienced an issue with setting Sprint Dates where the Jira trims the century digits?

Question

Our cloud solution install has a bug where you set dates for a sprint and every so often it will trim the century.

so 01 June 2023 08:00am becomes 01 June 23 08:00am

This is fine except Jira translates it to 01 June 0023 08:00am which obviously causes a lot of issues!

Is there a configuration setting to fix this or is this a jira bug?

Trudy P Claspill · Answer

I think I found the problem. I was able to recreate what you experienced.

In the Date/time Format settings I changed years to 4 characters.

I then modified the General Configuration / Advanced Settings.

I set the year to 4 characters here:

And left the year set to lower case "y" here:

Then I had the same experience as you.

If I changed the second format to use an upper case "Y" instead, then the dates for Sprints displayed the correct century.

Phil_2njbbl · Answer

Trudy, thank you but no love.

When creating a sprint, we use the calendar function which populates only the last two digits.  01/Jun/23. This looks perfectly valid. But when I save it, it converts it to 01/Jun/0023.  This happens regardless of the format prescribed above.  Whether I choose the format to be yy or yyyy, the result is the same

Trudy P Claspill · Answer

Hello @Phil

I have not seen the dates being sporadically trimmed like that, but there is a global setting for how dates should be displayed.

You would find that under Settings (gear icon) / System / Look and Feel / Date/time Formats