Cannot import estimates that are 0.5d - seem to round down to 0.43d

[Ben Tarrant]

We plan large amounts of work in excel and then import them into Jira periodically. We tend to run our estimates in 0.5d, 1d, 1.5d etc.

Our issue is that whenever we import tasks that have .5 in the estimates, Jira is converting that into .43 somehwat inexplicably. A few data points to raise:

• We operate on 7 hour work days, so 0.5d is equal to 3.5 hours or 25200 seconds
• The math we are doing is d*25200 = estimate in seconds
• We import the estimates in seconds
• On the sheet, 0.5d is shown as 12600 seconds (or 3.5 hours)
• When imported, Jira changes this to 0.43d and when reviewing the XML output, the estimate is forced to 10800 seconds (or 3 hours)

My question is - why is Jira forcing the estimate of half a day down to 3 hours and not 3.5 hours when the working hours is 7, not 6? This has been driving us insane for weeks, any help is most welcome!

[Ben Tarrant]

[Hannes Obweger - JXL for Jira]

Hi @Ben Tarrant

welcome to the community! 

This is mysterious indeed. Have you reached out to Atlassian Support about this? Please keep us posted on what they say.

I don't know if this justifies additional tooling for you, but just to put it out there in case it is useful: If you're open to solutions from the Atlassian Marketplace, 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 issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

This is how it looks in action:

This all happens directly in Jira, on live Jira data - so there's no need to sync back and forth between Jira and Excel. If you still prefer to work in Excel, you can also copy/paste data from Excel straight into JXL, without any odd conversion errors.

Any questions just let me know,

Best,

Hannes