Skip to main content

Community

Connector Improvement: Azure DevOps CAPACITY Table Sync

Not planned

Please sign in to leave a comment.

Comments

3 comments

  • Official comment
    Vishal Ray User

    Hi Tony,

    Thank you for raising this request - adding Capacity support would be a valuable improvement for understanding team availability versus planned work.

    From our review, Capacity is closely tied to Iterations (Sprints) in the Azure DevOps API:

    • Capacity: https://learn.microsoft.com/en-us/rest/api/azure/devops/work/capacities?view=azure-devops-rest-7.1
    • Iterations: https://learn.microsoft.com/en-us/rest/api/azure/devops/work/iterations?view=azure-devops-rest-7.1

    To ensure we capture the full scope, are there any additional Azure DevOps objects you depend on to support your capacity-vs-planning workflow?

    Your input will help us size this feature appropriately.

    Thank you,
    Vishal

    Most of what we get out of iterations already comes from Work Items aside from the effective time period and the capacity of each team member. We can derive the time period because we generally have consistent sprint lengths, but that'd be helpful at an iteration level as well.

    Thanks for asking the follow-up.

  • Vishal Ray User

    Thank you, Tony, for your quick response. I will add this to our backlog and update you when we prioritize to pick this update to Azure DevOps.