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.
Hello
For my testing purpose, I would like to create a jira ticket for which created date is in future.
I used csv import and in the file i put created date as 9/1/2022 and imported using mm/dd/yyyy format.
When the ticket is created after import I see created date as Jan 1 2022, instead of expected sept 1 2022
Is there a issue creating tickets with future created dates?
Please let me know
Abe
I have the same issue using JSM 4.20.8. After CSV import using the same date format as excel "dd/MM/yy h:mm" or even when trying ""dd/MM/yyyy h:mm". For some reason it imports successfully, but that date is set for a year in the future! It should import as 5/26/22 or 5/26/2022, but it imports as "1/5/2021" or "12/5/2023" or "8/5/2023".
Yes, all 3 records that was imported with the same created date, imported with 3 complete separate created dates set for the future. Is their a known defect that I'm not aware of?
Thanks!
Hi,
did you ever work out how to get around this? I have the same problem. Importing small amounts by CSV and the dates go crazy in to the future. The created date is ok, its the comment dates.
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.