nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Due date inconsistency when I try to set a date after 20 years from now

Baskar Palanisamy

For one of my issues, when I try to set up a due date as 12th Feb 2054 using the inbuilt Jira calendar, I was able to select the date in the calendar. However, when I click outside to save my changes, the year automatically changes from 2054 to 1954.

I did some trial and error to understand the breaking point, and I noticed if the year that I select is below 20 from today, the year section saves correctly. If it is more than 20, the first 2 digits in the year parameter automatically changes from "20" to "19".

Can someone please suggest me what's causing this, and how can I fix this issue?

Appreciate your time for reading this!

Accepted answers

Karan Sachdev

Hey @Baskar Palanisamy

Welcome to Atlassian Community!

Strange behaviour, but I am able to replicate this. Anything up to 31st Dec 2044 works fine. 1st Jan 2045 onwards goes back to 1900s.

Might be a limitation, I'll try to find some documentation on this or check internally to get more insights into this behaviour.

You may also report this to our support team via a support ticket.

Thanks!

All comments

Karan Sachdev

Hey @Baskar Palanisamy

Welcome to Atlassian Community!

Strange behaviour, but I am able to replicate this. Anything up to 31st Dec 2044 works fine. 1st Jan 2045 onwards goes back to 1900s.

Might be a limitation, I'll try to find some documentation on this or check internally to get more insights into this behaviour.

You may also report this to our support team via a support ticket.

Thanks!

Bill Sheboy

Hi @Baskar Palanisamy -- Welcome to the Atlassian Community!

Adding to the answer from @Karan Sachdev ...

That is a known problem, and here is the defect for it, which has timed-out and been closed: https://jira.atlassian.com/browse/JRACLOUD-82550

Kind regards,
Bill

Baskar Palanisamy

Thank you @Karan Sachdev @Bill Sheboy for promptly replying to my query.

Appreciate your time once again!

Karan Sachdev

Hey @Baskar Palanisamy

As @Bill Sheboy pointed, this happens to be a known issue. Though the bug was closed, we have a suggestion ticket for this. There's a workaround suggested which worked for me:

As a admin, go to System Jira Settings.
Click on Advanced Setting.
Update jira.date.picker.java.format from any 2-digit year formats to a 4-digit year (e.g. `d/MMM/yy` to `d/MMM/yyyy`).
Update jira.date.time.picker.java.format from any 2-digit year formats to a 4-digit year (e.g. `dd/MMM/yy h:mm a` to `dd/MMM/yyyy h:mm a`).

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-software%2ccloud