Why does issue import divide time values by 60?

Alex Marschner January 18, 2019

On JIRA v7.12.1, when I import an issue with "28800" in the "Original Estimate" field, I expect the issue to have an original time estimate of one eight-hour day (ie 28800 seconds).  However instead it has a value of eight minutes! ("8m")

When I multiply the time value by 60 and re-import, the original time estimate is 1d.

Why is the import function dividing the 'seconds' time import by 60?

2 answers

0 votes
Nikesh Maharjan February 11, 2022

I'm having the exact same issue while importing.

0 votes
Kian Stack Mumo Systems
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 18, 2019

Alex, 

This is not expected behavior. JIRA should be respecting second by default on import. How are you importing them? 

Thanks, 

Kian

Alex Marschner January 18, 2019

Kian,

I am importing via the Issues -> Import Issues from CSV menu function.  I have attached the .csv and the saved config settings (.txt).  You will have to modify the CSV for the Assignee name and the config settings for the project information.

(edit - I will put the text of those two files below, as I don't see an 'attach file' ability)

Alex Marschner January 18, 2019

{
"config.version" : "2.0",
"config.project.from.csv" : "false",
"config.encoding" : "UTF-8",
"config.email.suffix" : "@",
"config.field.mappings" : {
"Assignee" : {
"jira.field" : "assignee"
},
"Issue Type" : {
"jira.field" : "issuetype"
},
"Description" : {
"jira.field" : "description"
},
"Fix Version/s" : {
"jira.field" : "fixVersions"
},
"Parent Id" : {
"jira.field" : "subtask-parent-id"
},
"Summary" : {
"jira.field" : "summary"
},
"Issue Id" : {
"jira.field" : "issue-id"
},
"Epic Name" : {
"existing.custom.field" : "10103"
},
"Original Estimate" : {
"jira.field" : "timeoriginalestimate"
},
"Epic Link" : {
"existing.custom.field" : "10101"
}
},
"config.value.mappings" : { },
"config.delimiter" : ",",
"config.project" : {
"project.type" : null,
"project.key" : "ETF",
"project.description" : null,
"project.url" : null,
"project.name" : "Engineering Tool Flow",
"project.lead" : "AMarschner"
},
"config.date.format" : "dd/MMM/yy h:mm a"
}

Alex Marschner January 18, 2019

Issue Id,Issue Type,Epic Name,Assignee,Original Estimate,Summary,Epic Link,Parent Id,Description,Fix Version/s
1,Epic,Test Import Epic,AMarschner,,Test Import Epic 2,,,Epic with some stories under it,
2,Story,,AMarschner,28800,Test Import Story 3,Test Import Epic,,Story with some subtasks under it,
3,Sub-task,,AMarschner,,Test Import Subtask 7,,2,"Sub-task, where the real work gets done",

Alex Marschner January 22, 2019

If you try to do the import using the above data, does it also do the divide?

Suggest an answer

Log in or Sign up to answer