Burndown: "RTE change" vs "Work logged"

[Jen]

Hello!

I'm trying to analyze my team's burndown chart so I've been reviewing the day-to-day breakdown below the chart and there's a pretty even mix of the two event types "RTE change" and "Worked logged". 

The screenshot I included is for one ticket over the course of two days. When I dig into the ticket's History, Activity, and Worklogs- things just don't quite match up.

I've asked the developer who worked on the ticket and they use the same exact method to log time, every single time. So I really don't understand why there are two event types.

We use Tempo to log time, is this just some kind of delay in how Tempo and Jira interact with each other? Or is there any other kind of explanation?

[John Lee]

@Jen Chau have you found the answer? im having the same challenge to analyze the behavior of the RTE line in burndown chart..

[Jen]

Hi @John Lee

Yes, actually I've since discovered that it really is just a delay between Tempo and Jira. Work logged appears to be a Tempo event type and RTE change appears to be a Jira event type. I haven't taken the time to figure out what the exact cadence is, but logged time in Tempo will accumulate up to a few days before being officially carried over to Jira. 

[John Lee]

@Jen Chau Thanks for the reply!

Yes, my team is using Tempo to log time against their JIRA issue too. I have the same findings as per yours, there's a delay to reflect in "RTE change" after my "Work logged" is done.

[John Lee]

@Jen Chau i also came across this, not sure if it's because of the Tempo setting, you might want to check out the comment from the post below.

https://community.atlassian.com/t5/Jira-Software-questions/Burndown-chart-does-not-include-worklogs-reported-by-Tempo/qaq-p/43673

[Kerry Ayers]

I am working on the same question (diff between RTE change and work logged); however, we do not have Tempo.  This isn't related to use of Tempo.