Planner feature
Convert Jira Story Points to Hours and See Real Capacity
Your team estimates in story points, but capacity is counted in hours. ActivityTimeline converts each Jira issue's story points to hours with a rate you set once, so the Planner shows real workload and available capacity for every person.
30-day free trial on the Atlassian Marketplace.
What Is Story Points to Hours Conversion?
Story points to hours conversion is a rate that turns the story point estimate on each Jira issue into hours, so the ActivityTimeline Planner can calculate workload and available capacity for every person. You set it once for all projects, or per project.
There is no universal rate. Each team picks its own from past sprints, for example 1 story point = 4 hours, and adjusts it as its pace changes.
ActivityTimeline is a resource planning, capacity management and time tracking app for Jira. With the conversion, each issue keeps its story point estimate, and the hours feed only the workload indicator, available capacity and reports.
Try it: pick an estimate, a rate and how many days the issue is scheduled.
Why Convert Story Points at All?
Story points measure complexity, not time, and pure Scrum keeps it that way. That works inside one team. In a large company it breaks: each team sizes a point differently, and people work for more than one team. To see whether one person is overbooked, you need a shared unit. Hours are that unit.
Teams keep estimating in points. The rate is only the bridge that lets you compare them.
Example: Emma works for two teams in one two-week sprint.
Web team
40 h
10 SP × 4 h per point
Mobile team
48 h
8 SP × 6 h per point
Emma in points
18 SP
Says nothing about her sprint
Emma in hours
88 h of 80 h
Overbooked by 8 hours
What Story Points to Hours Conversion Does
Set the rate once and every story point estimate counts in workload, available capacity and reports.
Set one rate for every project
A global rate in Configuration applies to every project estimated in story points. One change updates every workload that depends on it.
Give each project its own pace
A mobile team and a web team rarely burn points at the same speed. A project rate overrides the global one for that project only.
See capacity in hours, not guesses
Converted hours fill the workload indicator under each name and the capacity reports. Issues estimated in hours and in story points sit side by side.
How to Convert Story Points to Hours in Jira with ActivityTimeline
Three steps for an ActivityTimeline administrator. Your Jira issues and estimates stay as they are.
Step 1 · Set the global rate
In Configuration → General, define how many hours one story point means, based on your past sprints.
Step 2 · Override it per project
In Configuration → Projects, click Manage next to a project and give it its own rate. If both are set, the project rate is used.
Step 3 · Plan on the timeline
Schedule issues on the Planner. Their converted hours spread across the scheduled days and fill each person's workload.
Planning only in story points? Story points don't shrink when time is logged, so set the Time Tracking Mode to Users do not log worked time and the effort stays spread across the whole issue.
Story points conversion in the Help CenterWatch the short setup videoStory Points to Hours FAQ
What Scrum masters and resource managers ask before they plan with points.
Still have a question?
Ask us in a 25-minute demoEstimate in Story Points, Plan Capacity in Hours
Set your conversion rate on your own Jira projects in a 30-day trial, or let us walk your team through it in a 25-minute demo.
30-day free trial on the Atlassian Marketplace.
Questions first?
Contact us through the support portal