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?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

590 views 0 6
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you