Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
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

Join now to unlock these features and more

Burndown Report for Sprint does not show accurate values

Judy Colonero
Judy Colonero Sep 24, 2019

 

On the burndown report for TP-60 it shows there is 2d 7h 15m remaining. 

On the actual story:  Estimated = 5h, Logged 4h, Remaining 1h -- this is correct.  

 

How can the report show that there is 2d+ remaining.  This is misleading to management who periodically reviews the sprint burndown report.  

 

Any help is greatly appreciated. 

Thank you,

Judy

 

Comment
Watch
Like Be the first to like this
325 views

1 comment

Judy Colonero
Judy Colonero Sep 24, 2019

It also states in the Event Detail of the Sprint Report:

"Remaining Time Estimate changed from 5h to 1h".

Like
Reply

Comment

Log in or Sign up to comment
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

See all events