Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-74324

Average time in status gadget calculation is incorrect

XMLWordPrintable

      Issue Summary

      The gadget "Average time in status" is not providing the results as described in its description:

      Displays the average number of days issues have spent in status.

      When comparing the results with manual calculations there is a big difference in which I am not able to explain how this has resulted.

      • Also, important to add that this gadget only consider issues that were resolved in the same period (whether you're using Hours or Days)

      (On a side note, this gadget is also not listed in this list from our knowledge base).

      Steps to Reproduce

      1. Choose 3 tickets that were in the same status for some time
      2. Resolve those 3 tickets
      3. Create an "Average time in status" that filters the tickets you resolved
      4. Verify the results within the gadget and compare with your own average calculation

      Within my tests, I had the following values for time spent in the "To Do" status for each ticket, these were the only resolved tickets within that day on my filter:

      • ABC-1
        12.08	total days  or,
        289.84	total hours
        
      • ABC-3
        12.08	total days
        289.95	total hours
        
      • ABC-4
        12.08	total days
        289.85	total hours
        

      Expected Results

      The gadget would do the following calculation:

      Where:
      T = time spent for that resolved ticket in the 'example' status
      N = Number of tickets closed on the respective period
      (T1 + T2 + T3...) / N

      So for the above example using days as period we would expect 12.08 days of average

      Actual Results

      These are the results obtained from the Gadget:

              Unassigned Unassigned
              emasiero Eduardo Masiero
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: