Issue getEstimate() API possibly incorrect.

The Issue API

States that

  • the "remaining estimate" of work left to be performed on this issue, in milliseconds.

However in development, I am finding that it is actually providing the "remaining estimate" in seconds?

Have I done something stupid, or are the docs wrong?



2 answers

1 accepted

This widget could not be displayed.

I've researched this further and am now convinced that Issue:getEstimate() returns seconds, as do other time based methods such as Worklog:getTimeSpent()

It is possible this is an option that can be changed, but regardless the API is not accurate.

My concern now is that after writing the plugin to deal with seconds, Atlassian will change the method inline with the API docs and break my plugin.



This widget could not be displayed.

i think getEstimate() will return milliseconds only,

on which jira version you are testing on?

I suspect the docs are in fact correct, but I can't work out what I'm doing differently.


I am using the Report Module and printing out issue.getEstimate() in a velocity file. After setting remaining time to 1 Hour, it prints 3600, which is clearly 1 Hour in Seconds.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

150 views 1 3
Join discussion

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