To view metrics for the tickets in your Space, you must be an Owner of that Space. Open the Tickets tool and then click on the Metrics sub-tab. You’ll then be able to toggle through the various metrics available using the sidebar on the left of the screen.
Cumulative Flow Diagram
This chart shows the number of tickets in each status column over time. You can see work in progress, velocity, and bottlenecks. This report shows the shape of your iteration, Scrumban sprint, or Continuous/Kanban WIP. It requires a current milestone.
Velocity
This chart shows the estimate value completed in a rolling 4 week interval. Use this report to monitor performance from week to week. For more information, check out Utilizing "Velocity" Reporting.
Burndown
This chart is a representation of work remaining versus time. Use this report to monitor the progress of a Scrum sprint or release iteration.
Cycle Time
See how fast tickets move from concept to implementation in your current workflow. Understand where the process slows down and improve those parts using the Cycle Time report.
Tickets by User
This chart shows the tickets assigned to each user. Click on a username to view a detailed user activity report. Use this report to balance load and report on productivity.
Tickets by Status
This chart shows tickets organized by status. Click on a status to see a detailed ticket list. Use this report to monitor work in progress.
Tickets by Priority
This chart shows tickets grouped by priority. Click on a priority to see a detailed list. Use this report to track important tasks.
Stuck Tickets
This chart helps to identify tickets that are have not changed status in X days (the number of days is customizable. Use this report to manage work in progress and find problems.
Dependency Report
This chart helps identify tickets that are not progressing due to a dependency on another ticket. Use this report to find the critical path items that people are waiting for.
Blocking Tickets
This chart helps identify dependent tickets that are not progressing because the preceding ticket is not assigned, not in the current milestone, in lower priority, or stuck. Use this report to identify potential bottlenecks.
Need help? Please contact us at support@assembla.com.