You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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:
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.
Number 5 in your answer relates for you configuration of Jira. It may not work for other users.
Anyway thank you for your answer.
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.
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.
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.
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."
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:
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!