large_DALL·E 2024-11-16 20.04.19 - A sleek, modern office setting with a group of diverse professionals collaborating around a futuristic glowing data display screen. The screen shows c.webp

medium_DALL·E 2024-11-16 20.04.19 - A sleek, modern office setting with a group of diverse professionals collaborating around a futuristic glowing data display screen. The screen shows c.webp

small_DALL·E 2024-11-16 20.04.19 - A sleek, modern office setting with a group of diverse professionals collaborating around a futuristic glowing data display screen. The screen shows c.webp

thumbnail_DALL·E 2024-11-16 20.04.19 - A sleek, modern office setting with a group of diverse professionals collaborating around a futuristic glowing data display screen. The screen shows c.webp

DALL·E 2024-11-16 20.04.19 - A sleek, modern office setting with a group of diverse professionals collaborating around a futuristic glowing data display screen. The screen shows c.webp

Can't find the story points field in Jira? Step-by-step guide to enabling estimation in both Company and Team-managed projects—plus the field name difference that trips everyone up.

Jira-Project-Settings-Enable-Estimation-Feture.webp


## 2. Adding the Story point, T-shirt estimate and Estimated By fields to individual Jira issues
These fields don’t show if they haven’t been added before. To add them you need to place them on the screen for each issue type you are going to estimate. Here is how this is done:

**Open the Field Configuration in your Jira Project**
You can access this screen either by using:
**Left hand sidebar - Menu**
### A. Navigating to **Project Settings** _(if you haven't done so already)_
![Jira-Opening-ProjectSettings-TeamAndCompany-Managed-Project.png](https://res.cloudinary.com/smartguess/image/upload/v1741860951/Jira_Opening_Project_Settings_Team_And_Company_Managed_Project_e40eeffdcd.png)
### B: Select the **Issue Type** you want to edit
![Jira-Project-Settings-Open-Issue-Type-Story.png](https://res.cloudinary.com/smartguess/image/upload/v1741861022/Jira_Project_Settings_Open_Issue_Type_Story_c77cda91e4.png)

**OR - another way**
### B1 With a Jira Issue Open - click the Configure button in the bottom - right corner
![Jira-Open-Configure-Fields-From-the-Jira-Issue.png](https://res.cloudinary.com/smartguess/image/upload/v1741861121/Jira_Open_Configure_Fields_From_the_Jira_Issue_83863875c1.png)
### B2 The issue type of the issue you had open is automatically selected
__


** This will open up the following screen allowing you to add fields to the screen:**


Jira-ProjectSettings-IssueType-Field-Configuration.webp

**Find the field, then Drag and Drop**

### C. With this screen open, find the fields to add, then use Drag and Drop to place them on the screen.
![Jira-Fields-Search-Box.png](https://res.cloudinary.com/smartguess/image/upload/v1741861469/Jira_Fields_Search_Box_5fb4c5ca8d.png)

Use the search box to **Find the field to add** using the following field names,
- The Estimated by field name is "Estimated by"
- The T-shirt estimate field name is **"T-shirt estimate"**
- For Team managed projects the field name is **"Story point estimate"**
- For Company managed projects the field name is **"Story points"**

### D. Use drag and drop to place the field in your issue view
Here is how this is done for the "Story" issue type:

Jira-Add-StoryPoints-to-Issue-Type-Still-Image.png

### E. Repeat the previous step for every Issue Type you use for estimation
Notice the video above showed field added for the "Story" - issue type. Repeat the process for every issue type you use to estimate Story points for (Epics, Bug, Task, etc).

## 3. Saving Story point estimates 
Now that you’ve enabled the Story Points field in your Jira issues, there are several ways to add story points:

### A. **From the Backlog:** Click the story point field in the backlog view and enter your estimate:

Jira-Backlog-Add-Story-Point-Estimate.png

### B. **From the Issue View:** Edit the story points field directly in the issue details:


Jira-Issue-Details-Add-Story-Point-Estimate.png

### C. During Sprint Planning - In Smart Guess - save with on click
When Estimates have been shared with the team, use the *Set Story points to* button to save estimates with one click.


Jira-Backlog-SmartGuess-OneClick-Save-Story-Point.png

## 4. **Run One-Click Planning Poker from the Jira Backlog**
Jira itself doesn’t provide a built-in way to facilitate the Planning Poker estimation process beyond setting the final Story Point value your team agrees on. That’s where Smart Guess steps in, offering a seamless and intuitive solution.

With Smart Guess, your team  estimate stories directly from the Jira Backlog, using all the context and information already available in Jira. This eliminates the need to switch between tools, ensuring your estimation process is efficient, collaborative, and stays integrated with your existing workflow. Here is how it works:



How Smart Guess One Click - Planning Poker works

How_Smart_Guess_works.png

### A. Setting up your estimation card deck in Smart Guess:
To configure your card deck click the Manage Cards - cog wheel in Smart Guess:

Smart-Guess-ManageCards-CogWheel.png

This will open the "Manage Card Decks" screen as seen below, allowing you to fully configure the Card Deck: 
- Add cards you use
- Remove cards you don't use
- T-shirt estimation supported
- Multiple card decks are supported

Smart-Guess-ManageCards-Screen.png



## 5. Creating Story Point Reports
### Enable Reports in your Jira project
To use the Jira Reports, you'll need to enable Reports for your project, if you haven't already:
1. Navigate to **Project Settings > Features**
2. Find the **Report - section**, and **enable Reports**, as shown here:



Jira-Enable-Reports-Feature.png

Once the Reports feature is enabled you will find a "Reports" link in the left navigation of your project. Opening the Reports will give you access to the following reports to track your team's progress:
1. **Burnup report** Visulize sprint's completed work and compare it with its total scope.
2. **Sprint burndown chart** Track and manage the total work remaining within a sprint.
3. **Velocity report** Predict the amount of work your team can commit to in future sprints by seeing and reviewing total number of story points, i.e. teams velocity,  completed per sprint.


Jira-Reports-To-Track-Your-Progress.png

How to Add Story Points in Jira (2026) | Fix Missing Fields Fast

Flow Metrics shows leadership what you actually do: identify bottlenecks, improve predictability, and protect delivery. Turn invisible work into measurable results.
> "Finally, data that proves what I've been saying all along."

*Free trial available — no credit card needed 💡*  

Stop Defending Your Value. Start Proving It.

Turn Jira data into insights you can act on. Spot bottlenecks, track cycle time, and forecast delivery with confidence — all inside Jira.  

> “Smart Guess gave us instant visibility into our process. It’s the first time we’ve felt in control of delivery.”  

*Now available with a free trial — no budget approval needed 🚀*

See Your Team’s Flow Clearly.

Make cycle time, throughput, and WIP visible without spreadsheets or consultants. Smart Guess Flow Analytics shows where work really gets stuck — so you can act early.  

> “We cut weeks off our cycle time after seeing where work was really getting stuck.”  

*Free 30-day trial — see your flow in action 🔍*  

Uncover Bottlenecks Before They Hurt Delivery

Try One-Click Planning Poker you run from the Jira Backlog and you will never look back.

"After trying many tools in Jira, we landed on Smart Guess. It's the best app ❤️ we've ever used!"

Now available for free — no budget approval needed! 🚀


Transform your Planning Poker

Run one-click Planning Poker directly from the Jira Backlog and never look back. Estimate faster, collaborate better, and keep everyone aligned.  

> “After trying many tools in Jira, we landed on Smart Guess. It's the best app ❤️ we've ever used!”  

*Now available for free — no budget approval needed 🚀*  

Transform Your Planning Poker

Every missed deadline has a cause. Every blown estimate has a reason. 

But without connecting the dots across sprints, you're experiencing the same problems over and over.

We'd been underestimating integrations for 18 months. It was obvious once we could finally see it.

How Many Sprints Before You Spot the Pattern?

When stakeholders push for aggressive timelines, you feel the risk. 

But _"I think this is too ambitious"_ doesn't win arguments. Data does.

_"For the first time, I could show leadership exactly why their deadline was unrealistic—with numbers, not opinions."_

Turn intuition into evidence —free trial available 📊

You Know It's a Bad Estimate. But Can You Prove It?

Two 5-point stories. One takes 2 days, the other takes 2 weeks. Your team estimated them the same—but something made them wildly different. 

Without visibility into what, you'll keep guessing.

_"We discovered our 'quick fixes' were actually taking longer than new features."_

Stop guessing, start knowing—free 30-day trial 💡

Same Story Points. Different Outcomes. Why?

Dozens of estimation sessions per team. Hundreds of data points. All of it disappears the moment the meeting ends. What if that data could actually improve your predictions?

_"Years of Planning Poker sessions—finally doing something useful."_

Turn estimation history into foresight—free trial 🎯

You Run Planning Poker Every Sprint. What Happens to That Data?

Stakeholders add urgent work mid-sprint. You know it hurts delivery—but without concrete data, you can't quantify the damage or push back effectively.

_"Now I can show exactly how much longer planned work takes when we interrupt it with urgent requests. The conversations have changed completely."_

Quantify the true cost of interruptions—free trial  🎯

How Much Did That 'Quick Request' Actually Cost?

Story points tell you relative size. They don't tell you when something will ship. The gap between estimation and prediction is where promises break.

_"We went from 'probably next month' to '85% confidence by March 15th.' Leadership finally trusts our timelines."_

From estimates to predictions—start free 📅

Your Team Estimates. But Can You Actually Predict?

Issues sit in "In Review" for days. Blockers hide in "Waiting for Info" for weeks. 

Without visibility into time spent per status, you're managing blind. 

_"We discovered issues were spending 60% of their lifecycle waiting—not being worked on."_

See the truth about your workflow—free trial 🔍

Where Does Your Team's Time Actually Go?

Every retrospective, the same question: _"Why didn't we finish?"_ Without time-in-status data, you're debating opinions instead of analyzing facts.

_"Turns out our bottleneck wasn't development—it was code review. We never would have known without the data."_

Find your real bottlenecks—start free 📊

Stop Guessing Why Sprints Slip

Every process has blind spots. Time In Status reveals the delays your workflow has normalized—the ones nobody questions anymore.

_"At sprint end, our 'quick QA pass' was averaging 3+ days. Nobody realized until we measured it."_

Uncover what you've been missing—free trial 💡

It's Been In QA For How Long?

Every status change in Jira is a data point. But without analysis, it's just noise. 

_"We identified that issues with external dependencies spent 3x longer in 'Blocked' than internal work.\"_

Make your data work for you—free 30-day trial 🎯

Turn Status History Into Process Insights

using contentList for cta messages


https://marketplace.atlassian.com/apps/1225496/

Paid app

nav-try-button

SG-full-color-black.svg

SG-full-color-blue.svg

SG-logo-black-07.svg

SG-logo-color-05-MarketPlace.svg

SG-logo-white-06.svg

SG-full-color-white.svg

See what's unpredictable. Understand why. Fix it. AI-guided insights help you spot bottlenecks, reduce variation, and make estimates that actually hold up.

Estimate smarter together. Real-time collaboration meets historical data. AI-powered insights help your team calibrate estimates based on what actually happened, not just gut feeling.

How to Add Story Points in Jira

Story Points 101

Topics covered in the series

Popular posts

Explore More Ways to Improve Delivery

Flow Intelligence

Predictive Planning Poker