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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Burndown chart does not include worklogs reported by Tempo Worksheets



I'm evaluating the Tempo Worksheets add-on to JIRA/JIRA-Agile. I'm stucked with one problem related to work logging on issues, and I hope you can help me.

When any user logs its work on the issue using Tempo functionality (like 'tracker' or 'log work' from issue menu etc), the "remaining" and "logged" fields (on the given issue) are updated and it is possible to see the work log entries in Activity - Work Log. However the standard Burndown Chart (as well as Sprint Report) does not see any changes in logged hours / remaining hours. In Burndown Chart there is a list of events and the only event registerd is the sprint start (no 'work logged' or 'RTE change' events are displayed if made via Tempo Worksheets).

There is no problem if the user logs the work using standard JIRA time-reporting functionality. I attach few screens to visualise the problem.

The issue activity/work-log include all the worklog entries (issue: GD-1), but the Burndown Chart details includes only the entries registered with native Jira.


I'm trying JIRA/JIRA Agile 6.6.8 with Tempo Worksheets 7.12.


Any ideas what the problem might be?


issue timetracking.jpg

Issue worklog.jpg

Burndown chart.jpg

4 answers

Hi Tomek,

the default timestamp for worklogs made in Tempo is 00:00, so your Burndown chart will not show the hours logged in Tempo until the next day (it shows the logs until "now", so worklogs in Tempo will not be considered). To avoid this problem, please enable the "Log work with start time" feature in Tempo (Tempo Administration, Global Configuration, check the permission).

Kind regards,


It works. Thanks for the information/

Worked like a charm. Thanks!

I'm having a similar problem, using Cloud.  I don't have a Global Configuration option in Tempo Admin, and couldn't find a setting "log work with start time."  I found "Use start and end times when logging work" it was disabled, enabled it.  Was that the correct setting?

Rucha I'm New Here Jan 18, 2021


Could you find the solution to this probem?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

874 views 14 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you