Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why does JIRA accept 2 digit year values and place it in Year 00xx ?

Is there a way to modify the default behavior when someone enters in a two digit year to assume it's in the current millennium?

is there a way to post-date previous closed Sprints to fix our reporting?


1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 03, 2020

Hello Erik,

Thank you for reaching out.

Indeed, the selection of the wrong Millenium when adding only two digits to a date picker field is a reported bug with JIRA Application which our developers are already working on:

Default date format is two-digit and loses century chosen in calendar picker

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

In fact, this is related to a Java date bug, where it does not accept a two-digit parameter for the year.

Please, let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events