← Back to blog

Jira for estimates: what works and what doesn't

jira estimates tools

Jira is the most widely used project management tool in agile teams. It has native support for story points, velocity tracking, and burndown charts. But many teams tap into only a fraction of its potential — or worse, use it counterproductively.

What Jira does well

Native story points

Jira lets you set story points on every issue. The board shows points per column, and the sprint shows the planned vs. delivered totals.

Velocity chart

Automatic velocity chart by sprint. Just mark issues as “Done” and Jira does the math.

Automatic burndown

The Sprint Burndown is generated automatically as the team updates task statuses.

Planning board

Drag-and-drop issues from the backlog into the sprint, with real-time point counting.

What Jira doesn’t do well

Collaborative estimation

Jira doesn’t have efficient native Planning Poker. Teams end up using external tools (like Dev in Poker) and manually entering the points into Jira afterward.

Estimation disagreements

Jira records the final number but captures none of the discussion or disagreements that led to it. You lose the valuable context from those conversations.

Estimate comparison

There’s no straightforward built-in way to compare “estimated vs. actual.” It requires plugins or spreadsheet exports.

Custom fields

  • Story Points: Jira’s default field
  • Estimate confidence: custom field (High/Medium/Low)
  • Identified risks: free-text field

Workflow with estimation

  1. Issue created -> no estimate
  2. Refinement -> estimated via Planning Poker
  3. In Sprint -> estimate locked (changes require justification)
  4. Done -> points count toward velocity

Useful automations

  • When an issue moves to “Done”, add points to the sprint total
  • When an issue isn’t completed by sprint end, move it back to the backlog with a “carry-over” tag
  • Alert when the sprint scope exceeds the team’s average velocity

Integration with Dev in Poker

Recommended workflow:

  1. PO prepares items in Jira
  2. Team estimates with Dev in Poker (simultaneous, independent)
  3. Points are entered into Jira manually or via API
  4. Jira calculates velocity, burndown, and reports

This combination gets the best of both worlds: collaborative estimation plus sprint management.

Jira pitfalls

Micromanagement

Jira makes it easy to create dashboards showing “who delivered how many points.” Don’t do it. This breeds toxic competition.

Estimate inflation

When velocity becomes a performance metric, teams inflate story points to appear more productive.

”Original Estimate” field

Jira has a time-based estimate field in hours. Don’t use it alongside story points — it creates confusion between two different estimation systems.

Never-ending sprints

Extending a sprint in Jira because it isn’t finished is bad practice. Close the sprint, carry over unfinished work, and start a new one.

Useful plugins for estimates

  • Epic burndown: progress tracking per epic
  • Custom charts: personalized estimation dashboards
  • Velocity tracker: advanced velocity reports
  • Time in status: how long each issue sits in each column

Conclusion

Jira is excellent for tracking estimates and calculating sprint metrics, but it doesn’t replace a good collaborative Planning Poker session. Use specialized tools to estimate and Jira to manage the results.