The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Date format issue with Due Date

John Szczublewski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2014

I verified that all date formats ( advanced settings and look and feel ) are the same and correct.

MM/dd/yyyy and %m%d%Y as required.

If I enter 6/6/14 in the Due Date field, it's saved and displayed as 06/06/0014.

If I enter 6/6/2014 in the Due Date field, it's saved and displayed as 06/06/2014.

If I use the Date Picker dialog, the correct date ( 06/06/2014 ) is saved and displayed.

I have a user who doesn't use the date picker and forgets to enter the entire year when adding Due Dates to issues. I've had no luck finding a solution for this.

I guess I could change the date formats to yy instead of yyyy, but I hate to change the system for 1 user.......

Any ideas?

Thanks!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Dave Drexler
Contributor
September 29, 2014

Heh - Atlassian says this is "Not a Bug" https://jira.atlassian.com/browse/JRA-36354 

To accommodate the .0001-chance edge case of archaeologists using Jira, if you enter "14" for the year, it gets parsed to the year 14 A.D.

TAGS
AUG Leaders

Atlassian Community Events