What are the units for the Original Estimate field when importing from a CSV file?

This question is in reference to Atlassian Documentation: Navigating to the Import Wizard

The online Help file says it should be in seconds but when JIRA converts the value it divides the value by 3600 which converts it to hours or partial hours. For example I entered 86400 seconds which should be 24 hours but instead it converted it to 24 minutes at least that is what the Original Estimate field in JIRA is telling me.

2 answers

This widget could not be displayed.

I guess you probably opened CSV in Excel?

sometimes Excel makes wrong guess. please review your CSV using notepad - it may have proper data, in seconds.

Also worth noting that while importing CSV back to JIRA  it treats 1 day as 8 hours. 

This widget could not be displayed.

We double checked the CSV file in NotePad prior to attempting the upload and the value was in seconds.

The problem seems to be that during the upload JIRA is not properly converting the seconds to either minutes, hours, days, or weeks.

for example, we uploaded a value of 86400 seconds (24 hours * 60 min/hr * 60 sec/min) which should be 24 hours but instead it converted it to 24 minutes!

Hi Kevin, did you ever get an answer/solution to this? I am having the same problem.

Yes, at the time of the original issue, while the documentation stated that the import time was in seconds, in fact you had to multiply the seconds value by an additonal factor of 60 and use that value in the import! That was because the Import function was dividing the value by 60 while it was reading the file before recording the value. Obviously a "bug"!

Subsequent to the original issue, my organization updated JIRA to a new version and the "bug" was silently fixed! We are at v7.2.12 right now. Don't remember what version we were on with the origianl issue though.

Now the import treats the value read from the file as seconds and the import works correctly as documented. Of course not knowing that the "bug" was fixed caused an issue when we imported some tasks and found that now the Original Estimate values were too high! So we had to go back and adjust our template to not "overcorrect" for the original bug.

Ok, it looks like the bug is still there in the cloud version. 

Thanks for the reply. I'll use your solution in the mean time

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published 4 hours ago in Marketplace Apps

The 7 hacks of highly successful automation

...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...

26 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you