You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi.
I have a custom field (date type) in Jira service desk which is set to accept date of birth. The insertion will be done via API ( https://<OUR URL>/rest/servicedeskpi/request). When I am trying to insert dates which are more than 80 year (i.e. 1942 and below), the date is posted in the Jira form but it is increment with 100 (i.e. 1939-10-23 --> October 23, 2039). Dates starting 1943 and beyond inserts correctly.
How is this possible and perhaps, possible workarounds?
Thank you
So I just tested this with a custom date field on an issue create screen.
I could select a date before 1942 just fine (for example 1/1/1921), but as soon as I refreshed the page it changed to 1/1/2021.
So this has nothing to do with the API or even the date picker but everything with a limitation to how Jira stores dates it seems.
This is a known issue as mentioned here: https://community.atlassian.com/t5/Jira-questions/2029-Date-Bug-Fix/qaq-p/630830
The solution from that post is to update your Jira date format settings (you can find these under advanced settings in your Jira admin settings) to use yyyy for years instead of yy.
Cheers,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.