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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
If the main reason of using Story Points is to get team's velocity and plan future sprints correctly and resourcefully... why is it considered that only Stories should have Story Points?
Our sprints consists of Stories, Tasks, Bugs. How can we get team's velocity if only Stories will have Story Points
In continuation to your previous question, you have the option to add the Story Points field to other issue types like Tasks or Bugs. You can do that by modifying the screens used for those issue types and also looking at the context defined for the field story point. You can ask your Jira Administrator to do all that.
Jira won't stop you from using Story Point field in other issue types. You just need to spend some time working with your board to see how this field affects your way of planning.
I hope it helps.
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.