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.
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!
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.
So odd.. I have a bug with Server 8.0.4 where the estimates in seconds is not importing correctly.
On version 7.x.x I was able to take hours and X*60*60 and then imported that (as it is in seconds) and it worked correctly.
On 8.0.4 through some trial and error I had to modify to be X*60*60*3, and now it imports correctly.
Has anybody else seen this?
I can confirm seeing this for Jira Server V8.4: I need to multiply an hour by (3600 * 60) to get seconds in my imported Jira issues.
That's a pain in the neck, especially as this seems to be a recurring bug. For that (or against that, actually) there is regression testing.
This "phenomenon" forces me to "lie" in my import data!
We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...