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.
I am using the dd/Mmm/yy format - it works fine for target start and target end dates but not the Due field. It says unable to parse date no matter what format I use?
So I found the issue - have to remove the h:mmm from the config file format
Welcome to the community.
Please compare the date formats in csv for target start/end & due date. If format is identical, both columns should be imported as expected since there is no problem for target dates.
ps: I personally use 14-12-2022 / dd-MM-yyyy format for imports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Tansu
The format used in target start/end are identical to that used in due date, check ed by 3 people. Still cannot import to due date field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response, the date formats in both fields are identical, and have been checked by 3 people, target start/end imports fine, due date does not says unable to parse date.
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.