Time estimate field is missing.


Seems our version of jira and greenhopper is missing the estimate field that, I thought, was part of jira out of the box. Or with greenhopper.

I am currently running jira 4.3.4 and greenhopper 5.6.5

I have looked in the default field configuration and I do no see estimate or work estimate in the list.

Any ideas? We really need this feature for upcoming sprint.



3 answers

Did you turn on time tracking according to http://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking ? Please also make sure that the system field time tracking is enabled in your field configuration. more details at http://forums.atlassian.com/thread.jspa?threadID=53084
A detailled instruction how to add the time tracking fields to a screen can be found here: http://confluence.atlassian.com/display/JIRA/Defining+a+Screen#DefiningaScreen-AddingTimeTrackingcapabilitiestoascreen

This is a non-answer. I follow the three links on this page and I get led down a rabbit hole with no useful instructions on how to add estimates of time per task before work begins. This is a critical field. I can see that I can log work against an issue and it will reduce time from the estimate - but where is the estimate?

Justin Burke Atlassian Team Jan 07, 2016

The field is Original Time Estimate on the JIRA tickets. In the Agile UI, it is re-named Estimate and it will appear at the top of the issue details. You should be able to click and edit that field in-line.

It seems like this is true for Stories, but not Tasks. There does not seem to be a way to add Estimates to Tasks, unless I am missing something obvious. Is the point that all Tasks must be part of a Story, and only Stories have an Estimate, and the Tasks within that Story need not be tracked individually? Its pretty limiting if that is the case..

Woops just answered my own comment. If I change Estimation to "Original Time Estimate" rather than "Story Points", I can now see the Estimate option on tasks as well. This is very un-intuitive. The unit of measuring progress should not dictate whether or not a field is visible in an Issue!

I share the same sentiment with everyone in this thread. The WHOLE reason we're using JIRA is to track time estimates against the time logged for each issue, My God it's a PM tool for crying out loud. 

So Siddharth, how do I change Estimation to original Time Estimate rather than Story Points?


To change the estimation from Story Points to Original Time Estimate, go to the board configuration (not project configuration).


Hey Agile Enthusiasts,

I am using Story points as my Estimation Statistic and enabled time tracking to track the progress in sub tasks that contain hourly estimates. Now if PO creates a Task instead of a Story, I will not be enter the Story points to that as the estimate field is not available for Task issue types. So in order to enter storypoint estimation for a Task should I use the custom field - 'Story Points' ? 

But isn't this weird as I have already configured my board to use Story Points as estimation and the Estimate field is actually the story points field in the issue detail view.

My concern is would JIRA consider the story points in the "Estimate" field for "Stories" and the custom field "Story points" for "Tasks" issue types while calculating velocity ?

Your repsonse is appreciated !

Thanks in advance !


I am not sure that this is relevant anymore, but maybe will help other users who search for the same info...

You can indeed add story points to tasks or whatever issue type you like and use it as estimation statistics. Moreover, you can add any other numeric custom field and use as estimation statistics.


Like 1 person likes this

Just if it helps Estimate can not be changed (and will not be visible during Edit) if the item is in the active sprint.  You have to yank it out of current sprint, 'Estimate' and then add it back to sprint.

It seems once you have the custom field Story Points added to the board you also have to ensure that the Issues > Fields > Custom Fields > Story Points > Configure > Default Configuration Scheme for Story Points > Edit Configuration > Choose applicable issue types has the issues types you want to do estimation on selected. I only had Storys and had to select my other issue types.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

45 views 0 2
Read article

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