Ways to Track Capacity and Resourcing through Issues/Requests | Community
Skip to main content
Level 2
June 18, 2026
Question

Ways to Track Capacity and Resourcing through Issues/Requests

  • June 18, 2026
  • 1 reply
  • 0 views

Hi everyone,

I’m hoping there are some creative ideas out there that can help with better tracking capacity for one of our teams that only receive work through requests. 

We are tracking actual hours on these requests but planned hours are not included currently (and the team doesn’t want to track them at this time).   I have reports showing the amount of requests coming in to each person, amount completed, and actual hours reports but our leadership is hoping to see additional reporting for capacity and who is doing what. The planner and workload balancer cannot be used since these users only receive issues/requests and not tasks along with no planned hours. 

Any ideas to provide some additional reporting in our current state or are we stuck since we don’t use tasks or planned hours?

1 reply

ninoskuflic
Level 5
June 18, 2026

Hi ​@megand2, you are not completely stuck, but you cannot get true capacity planning without planned effort or available capacity data. 

 

You can maybe get the following metrics which might help:

  • “User A completed 35 requests requiring 120 actual hours” or
  • “User B has 25 open requests aging >14 days”

This can then give them an overview of where a disballance is happening. This is the only thing that comes to my mind at the moment while users are only working with requests. I do hope this helps even a little bit! 😁

If this solved your issue, please mark it as solved so others can find the solution faster.
megand2Author
Level 2
June 18, 2026

Hi ​@ninoskuflic, I appreciate you confirming I’m not missing anything obvious that can be done.  I have a report that shows the time to complete requests already but I like the idea of a user comparison of X requests taking X hours.   I’ll see if I can mock something up like that.   Not capacity planning really but maybe still good information at this stage that we can use.  Thank you!