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



I am new Scrum master and new in Jira also 

I am trying to make a good prediction of tasks during a Sprint for my team and I want to use the old sprint to make a realistic prediction. 

My question is if the calculation the velocity chart depending on the Story points number why jira doesn't cosider sub-tasks in the equations and put the Story (task type) to equal to 0 

Isn't that make the velocity chart not so accurate? 

1 answer

0 votes

Sub-tasks are not sprint-able items, they are a part of stories (which are).  You don't commit to sub-tasks, you commit to doing the stories, and estimates measure commitment vs delivery.

There are a number of ways of doing estimates on sub-tasks, but Jira has taken the simple route and does not support them at all.  In off-the-shelf Jira, don't put estimates on sub-tasks (or if you do, educate your users that they're nothing to do with your sprint velocity or progress) 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events