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?
I'm having the exact same issue while importing.
Alex,
This is not expected behavior. JIRA should be respecting second by default on import. How are you importing them?
Thanks,
Kian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
{
"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"
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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",
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you try to do the import using the above data, does it also do the divide?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.