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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,462,878
Community Members
 
Community Events
176
Community Groups

Estimating stories and tasks in the sprint.

Hi,

I have set of stories in sprint and tasks that are linked to stories not sub-tasks.

I use story points for estimates.

Now in the burn down chart it shows task and stories separately.

Is it possible like story 1- have 4 linked tasks.

Like 10 story points for Story 1 split up based on complexity to linked tasks.

Like Task 1 - have 2

task 2 have 3

task 3 - 4

task 4 have 1 story point so the sum up should be equal to story point of story?

And if 1 task is completed the story point should be burn down for both task and story.

Please let me know if this is possible and how to do it?

1 answer

0 votes

Hi @G Krithica ,

Unfortunately, no...I am not aware of any way to do this in Jira. "Task" and "Story" issue types are at the same level, hierarchically; meaning the breakdown for issue types is Epic ---> Story, Task, etc. ---> Subtask. There are only three levels, and Epic is at the top while Sub-tasks is at the bottom. 

The reasoning for having Tasks different from Sub-tasks and on the same level as Stories relates to the value the issues provide to the project. A Story is work that adds value, a Task is work that needs done but does not ad value, and a Sub-task is a piece of work within a Story or Task. 

If you use Portfolio you may be able to have them roll up to an Initiative and burn down from there, but I've never tried it. 

-Scott

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events