Due dates loaded up different from the original csv template

[Nicle Yang]

I imported some BAU tasks into jira from a csv template. The template was previously used for bulk upload. I changed the due dates of the tasks and saved a copy of the updated template as a new csv file, then uploaded. Interestingly, the due dates uploaded into jira are all wrong (i.e. still the old due dates prior to change). I went back to check the csv file uploaded and confirmed the dates in the template had been updated, however, the changes were not reflected in jira somehow. 

Anyone has any clue how this happened? what can I do to avoid the issue going forward? Thanks!

Nicle

[Ismael Jimoh]

Hi @Nicle Yang ,

From my understanding of the above the problem you have is, you have uploaded a CSV file with an updated due date via the CSV import but when you view the issues, the due date is still the same as the old.

Without understanding what CSV you uploaded, it could be difficult and other things to check will be:

1. The attempted update, was this using bulk issue create(found under Issue > CSV import),
2. Was the date format matching what JIRA expected?
3. Were there any warnings after you uploaded the files?
4. Was this meant to update an existing issue or create a new issue? (existing issues would require that you have the issue key present else JIRA would likely create a new issue)

Also, can you check the All tab under issue view for one of the impacted tickets to see if you made any change and if yes, what changed?

These will give you a hint of potentially what went wrong.

Cheers.