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

What is right size for Epic, Story, Task, Sub-task ?

Tridip Charukia
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 12, 2023

Hi Team, 

I have 2 queries if someone can help.

1. What is right size we should keep for each type of issue in JIRA?

For Example,

Max 10-20 Story points in each Story (1 Story Point = 1 day of work)

Max 20 Hrs for any Sub-task (Measuring Sub-task by Hrs)


2. What is the best way to decide to choose between Story and Task ?  













1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 12, 2023

Welcome to the Atlassian Community!

It's whatever size your team works with best.

Story points are not a measure of time though, please don't do that.  They are a relative sizing between issues, and have no link to time - your teams will regularly do things like logging 1 hour on an 8 point story and 12 hours on a 2 point story.  If you want to estimate in hours instead of relative sizing, either use the original estimate as the estimate, or create a numeric hour field.

The other two things you need to look at are:

  • The estimate for a story should be smaller than the size of the sprint - the whole point of a sprint is that you complete entire stories, so if a story is too big to do in one sprint, it needs to be split up into several stories (and maybe those contained within an Epic.
  • Sprint estimates do not go on to sub-tasks.  Sub-tasks are fragments of their parent, not sprint items.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events