How do you manage team capacity in Jira using story points and time estimates?

[Antoaneta Iskra]

Hi,

I’m trying to set up a better way to plan sprints and understand how work is distributed across the team. We use company-managed projects, and I’d like to estimate user stories with story points while tracking individual tasks using hours.

During sprint planning, I want to have visibility into each person’s workload in terms of available hours, while still being able to monitor team velocity based on completed story points over time.

I’m currently migrating from Azure DevOps to Jira, so I’m still getting familiar with how Jira handles these types of planning and reporting needs.

Is there a recommended approach or built-in functionality for managing this? Currently on Jira Standard, thinking of upgrading.

Thanks!

[Anastasia Andriyanova _Teamlead_]

Hi @Antoaneta Iskra,

Transitioning from Azure DevOps to Jira often comes with this exact challenge!

In Jira Standard, you can natively achieve this split by setting Story Points on parent Stories (for velocity) and using Time Tracking (Original/Remaining Estimate) on sub-tasks assigned to individuals. However, Jira Standard doesn't automatically roll up sub-task time estimates to give you a clear total effort view per Sprint without manual tracking.

Since you mentioned considering an upgrade: Jira Premium introduces Plans (formerly Advanced Roadmaps), which includes built-in capacity and workload management for teams and individuals in both hours and points.

However, if upgrading your entire Jira plan feels like overkill just to manage estimates and actuals across your hierarchy, a targeted app can bridge the gap.

(Disclaimer: I'm part of the Teamlead team behind TeamTime)

If your main pain point is tracking estimated vs. actual hours across tasks and sprints alongside Story Points, you might want to check out TeamTime. It automatically rolls up time estimates and worklogs across sub-tasks, stories, and sprint containers, giving you a clear view of remaining effort and progress ratios without messy spreadsheets.

Hope this helps you set up a smooth planning process!

[Mary from Planyway]

Hi Antoaneta,

If you’re coming from Azure DevOps, the main adjustment is that Jira separates velocity tracking from capacity planning a bit more.

Here's what I recommend:

• Use story points on user stories to track team velocity over time. Jira’s Velocity Chart and Sprint Reports are designed for this.
• Use time estimates on tasks/subtasks when you need to understand actual workload — for example, whether someone has enough capacity to take on more work during a sprint.

The tricky part is getting a clear picture of that capacity before the sprint starts. Jira shows what’s planned, but it doesn’t always make it easy to see how work is distributed across the team or whether someone is overloaded.

That’s where Planyway can help. It gives you a visual workload view on top of your Jira issues, so during sprint planning you can see each person’s available capacity, planned hours, and workload balance.

Workload is calculated based on set capacity, scheduled time, and estimation that can also be linked to Jira issues.

You can adjust assignments, move work around, and reschedule issues directly from the timeline while keeping everything synced with Jira.

A setup that works well is:

• Jira → backlog management, story points, sprint execution, and velocity tracking
• Planyway → sprint planning, capacity planning, and workload balancing