Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Adding and showing story points for tasks

My team are not building software for external customers. We want to use Jira for internal task and progress tracking. 

This means that many of our activities are not User Stories. They are Tasks. 

However I would like the team to get in to the habit of estimating the effort required to perform the tasks. 

Unfortunately I cannot see a way of displaying and using story points in Tasks, in the same way that they are used in Stories. 

I am using Jira Cloud.


7 answers

1 accepted

84 votes
Answer accepted

Thanks for pointing me in the general direction. However, your answer was a bit like RTFM.

The answer that I needed (now that I have worked it out) is:

  1. Select the Jira icon > Jira settings > Issues.
  2. Under FIELDS, select Custom Fields.
  3. Find the Story Points Field and note the Issue type(s) that are associated with it.
  4. To allow Tasks (or Bugs) to use Story Points open the three dot menu and select "Configure".
  5. Under the heading "Default Configuration Scheme for Story Points" select "Edit Configuration".
  6. Finally, find the heading "Choose applicable issue types" and select the Issue "Task" issue type is selected (along with Stories and Epics).

I have found lots of very very hard to follow posts like yours that have really wasted a lot of my time. Yours was the best but still hard work to follow.

As a Community Champion I would suggest that start by assuming that I have already searched google, and the community boards for an answer, and instead offer specific and useful help.


Nick Coster

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 18, 2018

Number 5 in your answer relates for you configuration of Jira. It may not work for other users.

Anyway thank you for your answer.

Like Adnan Cudic likes this

Thank you. Worked for me. 

Like # people like this

Thank you. It's work for me.

Like Nick Coster likes this

Super helpful. Thank you for taking the time to explain this so clearly. You rock.

Like Nick Coster likes this

@Nick Coster Thanks for explaining so clearly!! I didn't understand the Jira documentation.

Like Nick Coster likes this

Thanks, very helpful but I did have to dig around a little more to get this to work.


I think we wouldn't necessarily need Story Points for Tasks if tasks could be specifically made as a child of a User Story

Like Nick Coster likes this

The particular use case for me was unrelated to the user story format, otherwise I totally agree.  This was noted in the original question.

Since I posted the original in 2018 there may have been some changes that have left my answer out of date.

Like prakashkarkee likes this

@Nick Coster  Thank you very much it help me as a beginner. Though there is little change in 2020 jira cloud but process are quite similar.

Like Nick Coster likes this

@Nick Coster Thanks, I was really struggling with that one, appreciate the clear steps. 

Like Nick Coster likes this

Thank you for the original answer! Very clear steps I appreciate! 

Like Nick Coster likes this
Like Nick Coster likes this

Thanks! it works perfect! Thanks for explaining so clearly!

Like Nick Coster likes this

There are other ways to do this depending on your design flow but this method incurs minimal cognitive load. 

Like Nick Coster likes this

Thanks Danny.

For my brain, minimising cognitive load is a priority!


Like Danny O'Donovan likes this

@Nick Coster could explain more where these fields are visible:

Select the Jira icon > Jira settings > Issues

? I cannot find them so it's still unclear for me how to see Story Point in the Issue field :(

@Nick Coster Thank you!  Seriously saved me so much time with your answer (and you made me laugh).  Cheers.

Like Nick Coster likes this

@Nick Coster Solution is still working today.  Thank you.

Like Nick Coster likes this

Thanks @Nick Coster . I agree whole heartedly with your request for detailed click sequences to solve issues.

Like Nick Coster likes this

Thanks! This worked for me as well, I just had to make changes on a group of settings called context. I suppose this is only an update in the UI.

Brenda Oliveira
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 02, 2023


As Nick mentioned in his answer, Jira has changed a few things since this was initially posted.  For those who are searching for how to do this and might have stumbled across this post like I did, I figured I'd leave an updated answer for the convenience of others since this was the top result on Google when I searched. Here's how I did it in Jira Cloud as of February 2021.

  • Go to Jira Settings and then the "Issues" settings.
  • Select "Custom fields" under the "Fields" section on the left menu bar.
  • Find the "Story Points" field in the list and click on "X context(s)" under the "Screens and contexts" column.
  • It will show you the issue types for which the field is currently available.  Click on "Create, edit or delete contexts."
  • On the next screen, click the "Edit context" button next to to the scheme you're using.  (I only had one, but you may have more.)
  • On the next screen, in the "Choose applicable issue types" box, select all of the issue types you want to have the field.
  • Click the "Modify" button at the bottom when you're done.


You'll still have to add the field to the screens you're using and whatnot, but if you've already done that and it's not showing up because it's not applied to the specific issue type, this should fix it.

Thanks to Nick for his original answer that pointed me in the right direction.  Hope this saves someone a few minutes.

Thanks Mike for keeping the response up to date. I have been amazed at how popular my answer has become. It just goes to show that it is valuable to share our learnings with the community as we go. 

Like # people like this

Thanks Mike, it was really helpful.

Like Nick Coster likes this

All of these worked to get Story Points added to my Jira Cloud environment.  Thank you.  NOW .... My challenge is getting the Sprint efforts to drive towards zero like my Sprint Burndown Chart states.   

My Dev team also if very task oriented like the original post from @Nick Coster   I read somewhere that in my workflow story points should decreased as items are marked in a Resolved/Done status.

So I made my "Ready for Deployment" as a Resolved type status as items are staged for release.  My team completes tasks throughout the Sprint and items are then deployed on next to last day and Marked DONE if they also pass QA And or Product Owner approvals from the LIVE environments.

I thought changing my Ready for Deployment to a Resolved status would fix this issue,  But no.  My Remaining Sprint line stays pegged through the sprint cycle until fully closed on last day.  It kind of defeats the purpose of the Chart.

What am I missing?


I would create a new thread for this question, as it doesn't really fit the topic of this thread and likely won't get many views since this one is already closed with an accepted answer.  It will also help others in the future who may have the same question as you, since they'll be searching for your topic and not this one.

@Mike Conway Are those fields are available for non-admin project leads? where JIRA settings are accessible?

I'm pretty sure you have to be a Jira admin to change these settings.  The custom fields and such are an account-level thing.

The settings are under the gear icon in the upper right corner next to your name.  If you don't see it, then you don't have the necessary permissions.


Screen Shot 2021-11-09 at 8.13.46 PM.png

Thank you so much Mike!

Thank you, it works for me.

Just updating this in cases anyone using Next Gen struggles to find this answer as I did. Apparently, this has changed. At least as of March, 2021, this answer worked for me:

Here is the short answer from that page, but you should probably check out the whole answer yourself.

"There is no Estimation on the Agile Board for next-gen; the boards cannot be configured at all aside from adding columns and a bit of very basic automation.

To add the Story Points field to next-gen issue types, you don't need to do anything with the field context, nor do you need to manually add it to any screens. Go to Project Settings -> Features, then turn on the Estimation toggle. This will make Story Points visible on your issue screens."

1 vote
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 18, 2018


You should add the story points field to the screens for the Task issue type.

You can find more info here how to add a custom field to a screen:

0 votes
Jim Tafur
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Jul 14, 2023

Worked for me.  Thanks!

Thanks for the help.  Since this was written Jira has changed a few things, example under the three dot menu you no longer find "Configure" it is now "Contexts and default value", then under the heading "Default Configuration Scheme for Story Points" select "Edit Context" instead of "Edit Configuration". 

I appreciate the detailed explanation! That helped a lot!


Glad it could help! 

Suggest an answer

Log in or Sign up to answer