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,464,134
Community Members
 
Community Events
176
Community Groups

Burndown reports in jira

Hi all

I was wondering if it would make sense if the burndown reports (release / epic) used velocity to predict

Currently they require 3 sprints to predict, but we have many different initiatives that we break down in different releases and epic and I would like these reports to show the predicted burndown based on our velocity, maybe average over last n sprints (we look at past 6)

Either that, or on the report allow a velocity to be entered to trigger the prediction if required

I understand that driving if off the 3 sprints is the ideal, but at times it's good to get a prediction at the start, and sometime the work isn't much more than 3 sprints anyway

Thoughts?

0 comments

Comment

Log in or Sign up to comment