Avg time in status (instead of total time in status)
N
Nicolas Camhi
I would love to see the average time each task spends in each status (e.g. an onboaring funnel). As of now I could only find the total added time spent in a status by all tasks which is kind of pointless (attached image). This is a very basic KPI in project management.
Log In
P
Peter Locke
Lily Chan I found this when looking for how to do average time in status in the dashboard card. This is SO critical for understanding the performance of steps in a workflow. Please make it happen, or at least allow us to make it happen ourselves by letting time in status be something we can select in bar chart formulas with averages
Daniela Pelloso
It'll be very helpful!!
Lily Chan
Merged in a post:
Sprint Dashboards
N
Nate Goff
In 3.0 is there a way to see average times tasks spent in each active statuses at least in the current sprints. Bonus points if we can do a rolling average to see how we are trending (ex. tasks spent 27% longer in to-do during this sprint compared to previous)
-essentially, a better working version of this:
Lily Chan
Nate Goff We don't have this at the moment. I am going to merge this into the other existing request for being able to see average time in status.
Lily Chan
Merged in a post:
Average Time All Tasks Spent in Status - Widget (Response Time)
Derek Smith
Each task displays the amount of time it spent in any given status. Can we total all the time for Pending and divide by the number of tasks with a value for pending.
This would give me the average time a task spent in pending.
For us that would be used in our Dashboard as a 'response time'
If theres another way to do 'response time' (average time for all tasks between two dates, to go from pending to open) I'd love to hear from anyone that solved that.
Mike Coon
Agreed, I'm getting multiple requests from users that the total time in status dashboard card is functionally useless to them, because they really need average time to understand their performance.
For example, using a status like "Requested", if a team has an SLA of 48 hours to respond to requests, it's not useful to know total time in status. What they really need is to know that their average time in status for "Requested" was 72 hours or something else, so they can evaluate performance vs. SLAs.
This would allow them to find bottlenecks in processes. Step "X" in this process is consistently taking twice as long to complete as they estimated it should. What are next steps? That kind of thing.