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

Issue with burndown chart not reflecting time logged (for some users)

Logan Cummins
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!
Mar 29, 2023

We use our burndown chart to reflect the hours remaining for all of our sub-tasks/issues in a given sprint.  That functionality works fine, as sub-tasks move to "in progress" and "done" we have it set up to automatically reflect in the burndown how much time is remaining.  But my issue is that for certain users like myself (I am a project and board admin) no matter if it's a bug, story, tasks or sub-task, it won't reflect my time logged on the green line at the bottom of the burndown chart.  Although if you click into the issue from the "active sprint tab" for example, it will say that there is indeed time logged.  To make this more confusing, some of the developers on my team (I am a scrum master by the way), they can log "time spent" and it will show it as a little uptick on the green line I was referring to.  Is this a permissions issue?  I am a project/board admin and have access to edit/delete anyones work logs, so I would figure that I would have access to create my own issues or sub-tasks and even just log my own hours.   I've done multiple experiments with creating my own test issues and trying to get that green line uptick, but to not avail.  Does anyone have any idea what's going on here?  I'm trying to use this as a tool to track "time spent" on certain issues, not all issues.  I'm curious if anyone else has run into this.

2 answers

1 vote
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.
Mar 30, 2023

Welcome to the Atlassian Community!

Your case seems to be complex, but it is very hard for a lot of people to read the wall of text you have posted here.  I certainly can not make sense of it.

Could you explain the problem again, in one or two short sentences, so we can look at the basics, and then hone in on the actual fault?

0 votes
Danut M _StonikByte_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 30, 2023

Hi @Logan Cummins,

Try our  Great Gadgets app. One of the many gadgets that it offers is the sprint Burnup Burndown Chart. This gadget supports calculation method by time Remaining & Time Spent, and allows you to include the subtasks. This is how it looks like.


If offers also Release Burndown Chart and Team Velocity chart that supports time estimates and subtasks, which you might find useful.

If you have questions, please don't hesitate to contact

Thank you,

Danut M.  

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events