The CSV import appears to round Original Estimates down to nearest hour

I'm trying to import some tasks using CSV file import. I want to set original estimate which I understand is in seconds, but it seems to only allow a granularity of 1 hour. Is there any way around that please?

I'll paste my data and configuration below.

When I import the data I get 5 tasks created, only 2 of which have estimates. Test3600 gets an estimate of 1 hour. Test5400 also gets an estimate of 1 hour. It appears to be dividing by 1800 and then rounding down.

Please could you confirm if that is the case and advise on a workaround?

Many thanks

Greg

 

This is my data...

Summary,Estimate
"Test900",900
"Test1800",1800
"Test2700",2700
"Test3600",3600
"Test5400",5400

 

Here's my configuration...

{
"config.version" : "2.0",
"config.project.from.csv" : "false",
"config.encoding" : "UTF-8",
"config.email.suffix" : "@",
"config.field.mappings" : {
"Estimate" : {
"jira.field" : "timeoriginalestimate"
},
"Summary" : {
"jira.field" : "summary"
}
},
"config.value.mappings" : {
},
"config.delimiter" : ",",
"config.project" : {
"project.type" : null,
"project.key" : "blanked out",
"project.description" : null,
"project.url" : null,
"project.name" : "blanked out",
"project.lead" : "blanked out"
},
"config.date.format" : "dd/MMM/yy h:mm a"
}

 

2 answers

I have the same problem. I can't figure out how to import minutes... For example I have a task that takes 5,5h. I converted it to "5,5 x 3600" = 19800 but it imports to 5h.

Also, I tried 360000 and it imported to 100h. How can I import so it imports as days instead of hours?

 

0 votes

Unfortunately this is caused by a BUG. Please check the bug record below and mark yourself as a watcher in order to receive further updates about its implementation date.

https://jira.atlassian.com/browse/JRA-44971

Cheers

L.F

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 6 hours ago in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

17 views 0 3
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