Problem with Tempo and Worklogs Sync

[Joan Jaume]

Hello everyone!

Since this monday, 18/03, we have problems in our company with the syncronization worklogs in tempo. We add the worklogs in the tempo calendar, but these worklogs aren't showed and logged in the task.

The version of jira cloud is: 1001.0.0

And the version of tempo plugin is: 

version":"1.1.69-AC

Example:

Calendar

Task

Anyone know what might be happening? I have seen that tempo was updated on 14/03

[Susanne Götz _Tempo_]

Hi @Joan Jaume  and @Anatoly Kavun ,

Please note that the Work Time Calendar view shown in your screenshot is not part of Tempo.
Depending on the way worklogs are handled when created via this view, the worklog is not directly synced back to Tempo. The worklog will then only be shown in Tempo after a regular sync has been run.

Regards,
Susanne Götz
Tempo team

[Bogdan Podlesnii]

Most probably their problem is not related to calendar they are using, but to Tempo API, because we started facing the problems same time like they did and we are using just Jira API directly. 

BTW: should I create separate topic, because I'm afraid now my question will be lost and not answered by support team?

[Anatoly Kavun]

We are have the same problems.

[Rutger Deterd Oude Weme]

I´m facing a similar problem. We have developed a synch process between jira worklog hours and Noko as time tracking application. Since a month the tempo plugin is actived. Because of that worklogs in jira get the tempo user as author, so I had to change the filter to find issues with new worklog. The sync status is added to the worklog comment. This is still done by the jira api. But I don't see these changes in tempo. Could it be that the synchronization between tempo and jira is a asynchronous background process?

[Anatoly Kavun]

@Susanne Götz _Tempo_ 
Actually we have this problem when we use the smart commit from bitbucket to Tempo. But it started at the same time. And the reason, I think, the same.

[Susanne Götz _Tempo_]

It might be useful for both cases to create a ticket in our Tempo support so I can forward it to the development team to investigate if there is something on our side that affects this. 

In both cases ( using the JIRA API or logging via Bitbucket) the worklog is created within JIRA. If these worklogs are never synced to Tempo ( not even with a delay ) we will need to investgate this.

Regards,

Susanne 

[Bogdan Podlesnii]

Any updates of this topic? We are using our own software (https://github.com/zfmaster/uberigor) to automate scrum meetings worklogs adding. Last week everything was good and this week worklogs are simply not added. There is no errors returned from api, but also no records into tasks. 

We are using v2 API version: https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-worklog-post