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
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
I am trying to create issues from CSV with original estimate time included. (See picture 1 below) Tried to insert in 30m/30 minutes/30/1800 formats and none of it worked. When an issue is uploaded, original estimate stays 0 minutes. (See pic 2)
Can you please, assist?
Original estimate value needs to be specified as second.
I guess you properly match the original estimate field within import wizard. Did you have a chance to investigate detailed log file which becomes available after import process?
Also please take a look: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/
You should be able to import the issue with the Original Estimate. You should input the value in seconds
Here's the reference (https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file)
This is the page we get while importing
Sample CSV File
Summary,Issue key,Status,Original Estimate
Still seeing this issue. Terrible work around, multiply by an additional 60 to turn your minutes into hours.
So If I want a 2 Day estimate the math is: 2 Days * 8 Hours * 60 Minutes * 60 Seconds * 60 JIRA TIME = 3456000 JIRA Seconds.
I'm sure one day it'll be fixed and suddenly everything will be 60X too long, but we'll see.
@Dean Ritchie Yeey!!! This has been bugging me for hours now. Thank you very much for sharing the solution~ 😊
Edit: And it looks like everything changes again 😑. It looks like there's no longer a need for an additional "Jira Time" for importing CSV. Back to what it should suppose to, I guess.
I too ran into the need to use an extra Jira Seconds multiplier of 60 to get a proper number of "seconds" loaded into the OrigEst field, to show properly as my target number of hours in my tasks.
Then... I added Story Points to my CSV file, so I'm loading both OrigEst and StoryPoints. When doing this, I noted that my OrigEst hours were now off, too large by a factor of 60. It's as though adding the Story Points into the CSV load process somehow corrected the calculation of seconds used in the OrigEst field. Weird...
I would like to solve the issues in my software as Jira does: they removed the option to import the original estimated. When you find bugs, you delete them!! Easy busy!