Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-60841

Implement report for tracking time in status in JIRA

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 7
    • 6
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      Currently, there is no way of having a report generated to calculate how long an issue was in a particular status. This will help to identify best performers and issues which do not follow the correct timeline of an issue.

      Suggested Solution

      Implement reports that could:

      • Order issues by resolution time (to identify long running/complex ones)
      • Order issues by users and times they took to solve issues assigned to them.
      • Order issues by projects to identify what not keeping up with project timeline/delaying the project.

      Workaround

      To utilise the tab Transitions when viewing an issue. However, this is only available issue by issue.

            [JRASERVER-60841] Implement report for tracking time in status in JIRA

            Lars Olafsson added a comment -

            This would be great to have implemented. To be able to have time to market reports where it is possible to see and measure time from when an issue is taken out of the backlog, and work starts. So you are not reporting on the age of an issue based on when it was created, but based on when it was decided to start work on it.

            Or even if you are working with multiple teams, how much time does the issue spend in each status/transition/team, and how many times does it go back and forth between the two transitions. This could mean there is some issues with the quality delivered. E.g. if you have a transition called requirements analysis and one called devlopment. If it goes back and forth between these two transitions many times. Your requirement analysis is probably not good enough.

            Lars Olafsson added a comment - This would be great to have implemented. To be able to have time to market reports where it is possible to see and measure time from when an issue is taken out of the backlog, and work starts. So you are not reporting on the age of an issue based on when it was created, but based on when it was decided to start work on it. Or even if you are working with multiple teams, how much time does the issue spend in each status/transition/team, and how many times does it go back and forth between the two transitions. This could mean there is some issues with the quality delivered. E.g. if you have a transition called requirements analysis and one called devlopment. If it goes back and forth between these two transitions many times. Your requirement analysis is probably not good enough.

              Unassigned Unassigned
              nghanis Nithiyaa Ghanis (Inactive)
              Votes:
              22 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: