JIRA CSV Import does not import the Original Estimate values correctly. Why?

[Mark Hawkins]

I have an issue where I am trying to use the IMPORT CSV functionality against a JIRA project, to create issues and auto-populate their Original Estimate values. I have correctly followed the JJIRA formatting documentation here and here is a breakdown of my issue using screenshots: 

1. Import File: https://gyazo.com/3bb2e024fb72801a312b6e2b84563bae 
2. Board Original Estimate (after import) where I show what I expect to see as the values after an import: https://gyazo.com/e7b2d693c0b625d57f25a6f6f753e97e
3. My board settings: https://gyazo.com/861053e7fcb7d6a3cbe84e7864f3c47e
4. My Global Time settings: https://gyazo.com/d361b1f2a8546ead908e36ffb2a06ba3

My global work hours per day are 8hrs. As an example, I tested in this CSV import, where the original estimate value = 9000 seconds, yet after it imports it shows 2h against the Original Estimate field in the issue, instead of 2h 30m. In the same import file it successfully imports 18000 seconds as 5h.

Can anyone help advise why JIRA is incorrectly importing the original estimate data?

Thanks

Mark

[Tomislav Tobijas]

Hi @Mark Hawkins ,

We did big CSV import last quarter when migrating from another tool to Jira. We did experience some issues when 'translating' logged work values due to Tempo Timesheets app.
Basically, the underlying issue was with the global unit for time tracking settings, which was set to 'Days' instead of (default) 'Hours'.

Anyway, by the looks of it and as we're talking about estimates, this doesn't seem to be the case. 
If you would check what value is actually stored for each item displaying incorrect Original estimate (e.g. https://<sitename>.atlassian.net/rest/api/latest/issue/BJIT-82), can you check which value is stated there? (try searching term 'timeoriginalestimate')

To return to our initial issue, we had to debug this together with Atlassian Support and Tempo support team in order to find a resolution. So, it might be the best bet to try contacting them to see if they can see what's going on in the backend. 👀

Cheers,
Tobi

[Mark Hawkins]

Hi @Tomislav Tobijas - thanks for the advice, and we also use Tempo Timesheets. But I don't think the issue resides there, and at least I can't find a setting youb refer to - see here: 

1. Tempo Logging Time Settings: https://gyazo.com/fe98d377f98ea076a6665d589fc0d200

2. Tempo Story Points Settings (which we don't actually use, as we estimate in hrs & minutes): https://gyazo.com/e9ed528cddda40280021c2a265b7d5a2

I actually wasn't aware about the api JSON result you showed me now - thanks. But I can see there that it is importing as 7200 seconds instead of the 9000seconds in my import file - see here: https://gyazo.com/4f16d09b304f1c85f1a6ab769377b949

And the ones I expect there to be minutes, are importing as ZERO - see here: https://gyazo.com/31c119bcb69abd4d8ffffa1a4714f004

If you have any ideas please do share, otherwise I will also contact Atlassian support.

[Hannes Obweger - JXL for Jira]

Hi @Mark Hawkins

first off, I would definitely reach out to Atlassian Support. I don't see a reason why this wouldn't work natively.

Alternatively, if you're looking for an immediate solution, you may want to have a look at the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your work items (issues) that allows viewing, inline-editing, sorting, and filtering by all your work item fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable. It also comes with a long list of advanced features, including support for inline bulk editing via copy/paste. This works within JXL, but also across JXL and pretty much any other app, including e.g. Excel or Google Sheets. 

This is how it looks in action:

JXL generally accepts any value as it would be entered directly in Jira. So if there's a way for you to easily get the data into this shape, this could be a quick and easy workaround. 

I should also add that JXL can do much more than the above: From support for configurable work item hierarchies, to work item grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes