Overview

The Range Estimate add-on allows to set an estimate range for every issue - you can put Optimistic and Pessimistic estimate values. Actually, the add-on interprets the Original Estimate as the Optimistic value, so there is no need to duplicate the values when you start using the add-on with existing issues. For every issue, you can see how the logged time compares with the estimate range

The Range Estimate add-on also provides a set of JQL functions to help you with statistics and reporting

First Steps

To start using the add-on you don't have to do much. Just

  1. Install the add-on
  2. Add the Pessimistic Estimate field to the screens. Add-on adds a new locked custom field called Pessimistic Estimate to your Jira. You want this field to be available on edit screens of the desired projects to put your estimates in it. Please ask your admin to add the field to the screens
  3. To set your first Estimate Range, go to the issue and 
    1. set the value of Jira's system field Original Estimate (this is treated by the Range Estimate add-on as the Optimistic Estimate)
    2. set the value of the Pessimistic Estimate field

Next Steps

Make yourself familiar with JQL functions

The Range Estimate add-on provides a set of useful JQL functions which you can use to 

  • collect statistics on your estimates and analyze how accurate they are
  • detect problematic points of your project by tracking the issues where the amount of logged hours is 
    • much more than the Pessimistic Estimate
    • much less than the Optimistic Estimate
  • see which issues were done within the estimated range
  • detect potentially high-risk issues where the Pessimistic Estimate is much greater than the Optimistic estimate. This could indicate that the requirement is not really clear or that an additional research is necessary

Use JQL functions to track your project

You can benefit from creating a set of gadgets on your dashboards to track the time spent vs estimates. You can also subscribe to a filter to get an email every time the time spent on the issue is about to go over the Pessimistic Estimate. Lets see some examples

This set of gadgets on the dashboard below splits all the issues in the project by groups. On the left you can see how the Range Estimate JQL functions are used to configure these gadgets





issue in spentUnderOptimistic(0)




issue in spentInEstimationRange()




issue in spentAbovePessimistic(0)




issue in spentAbovePessimistic(100)

Another example of effective usage of the JQL functions is filter subscriptions. Create a filter like this 

statusCategory != Done and issue in spentInEstimationRange()

and subscribe to it.

You will get emails with the list of issues which are not yet completed, but the logged time is already between the Optimistic and Pessimistic estimate. This is the flag to pay close attention to these issues before it is too late - the time spent on these could get out of control pretty soon.