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

Time Tracking showing different Times for Work Logged and RTE Change Edited

Hi We are using Jira Cloud and have turned on Remaining Estimate and Time Spent to use for the burndown report.

When someone uses time tracking to log time And reduce the RTE, the RTE entry is logged at the correct time But the Work logged has a time in the past (which matches the work logged).

In the attached screenshot you can see 

1) EDWTSW-103 has 1d 10 min work logged (8hr 10 min)

The RTE Change is at  9:32 am but the Work logged is at 1:22 am  (8hr 10min earlier)

2) EDWTSW-83 4hr work logged 

The RTE Change is at  9:39 am but the Work logged is at 5:39 am  (4hr earlier)

I was expecting the Audit times for both events which were performed at the same time to be the same?

Jira work logged and RTE showing different times.jpg

1 answer

0 votes
Ivan Lima Community Leader Nov 02, 2020

Hi @Dean Margerison, when you log time on an issue, you can inform the date started, which can be in the past. In this case, your burndown chart will create an entry of the event type Work logged, and the event detail will describe the number of hours logged. Thus, the date in the burndown chart will be the same as the "date started" informed when you logged your time. This way, you have the flexibility to report your time in the past, which can fit in the sprint period.

The second entry you see on the burndown chart is the updated RTE, RTE change event, as a result of the updated time logged. In this case, the date is the actual date when time logged took place. The event detail shows the updated numbers for the RTE.

I hope that helps.

Are you saying that you infer the event time of the work by the current time - time logged? 

If so it might be a good idea in an edge case when a sprint has just ended but you still want to book time worked in that sprint.



For the vast majority of cases I believe in a burndown report if you see Time logged going up it would be better to reflect the reduction in RTE at the same point in time. Otherwise it gets difficult to understand what is going on.

Also If someone doesn't book time every day you could have the scenario where the Time Logged increase and RTE decrease are days apart

I would also argue that its wrong to assume that if I log 4 hours of work the start time of the that work is 4 hours ago. I'm assuming nobody is saying that you have to log the time immediately you have done the work.

Is there a way to ensure that both Time logged and the RTE reduction recorded at the same time?




Suggest an answer

Log in or Sign up to answer

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