JIRA 7 has landed! Are you an existing JIRA user with questions about upgrading? Visit the Migration Hub for information about upgrading to new JIRA applications

Skip to end of metadata
Go to start of metadata


As outlined in our docs, the resolution time is the difference between an issue's Resolution Date and Created date.

  • What about issues that get re-opened? How is the Resolution time calculated for this situation?
  • How are fractions handled? If the resolution time is 4/3 (1.333 days), do we calculate this as 1 or 2 days?


  • The Resolution time will be the difference between the latest, most recent Resolution Date and Created date.
  • Fractions of time are truncated. For example, the Average resolution of 1.7 days will get truncated to 1 day.


Help us improve!

Is this article helpful?
Is it well written?
Is the content complete?

  • No labels


  1. LAST meaning the "latest, most recent"

    1. Updated this article to reflect that clarification. Thanks for the feedback Matt.

  2. Is it possible to change the resolution time calculation to start not with the issue creation time, but rather with the time when an issue was transferred into a state?

    The use case is as follows - We use a kanban-ish development method, where we create most issues/featues/stories in a backlog upfront, thus killing the usefulness of the resolution time gadget. In our case, the lead/resolution time should rather be calculated using the time where an issue has been pulled to the selected issues. 

    As this calculation is the basis for multiple gadgets, maybe it could be changed per gadget in order to avoid unforeseen issues with other gadgets?

    Thank you

  3. Hello Jira, I would love to see an option for using the median instead of the average in the resolution time gadget. Since the distribution of resolution times is a poisson distribution rather than a gaussian, the median would be more meaningful especially for resolution times in the range of days. Regards, Christian

    1. You might find the Control report in GreenHopper useful since it shows each data point in the distribution. I also suspect the resolution time distribution is asymmetrical,  but have you seen any evidence or research on that?

  4. Can someone please confirm, is this report based on 7 or 5 day week, thanks

  5. What happen if the issue ticket has been put in "waiting for status" ... (this is the case where the assegnee asks some infomation more about the ticket to the reporter. The reporter's information are not enough)

    Is the "resolution time" calculated keep in mind that some ticket depend on more information by reporter?

  6. Can someone respond to above questions ? It's a valid and I'm looking forward for the same.