Worklogs can be created in either Tempo or Jira. Depending on where a worklog is originally created, data is synced between the two systems using a combination of webhooks and other technologies.
| Status | ||||
|---|---|---|---|---|
|
Tempo-Originating Worklogs
When By default, when a worklog is first created in Tempo, a corresponding worklog is created in Jira. This worklog is created without user attribution to respect view privileges for worklogs. Any update or delete action made to the worklog in Tempo is reflected in Jira. However, any changes made to the worklog in Jira are ignored in Tempo.
...
To avoid discrepancies in reporting, we recommend using Tempo Reports and the Tempo API for reporting.
If your organization uses Jira webhooks or other integrations that use Jira and/or the Jira API for reporting, please note that due to the discrepancies in how Jira-originating and Tempo-originating worklogs behave, there may be inconsistencies between these sources and Tempo reports.
...
As the worklog originated in Jira, any change made to the worklog through Jira is updated in Jira, as expected, and then synced to the Tempo worklog. Any change made to the worklog through Tempo is also reflected in Jira to provide a better user experience.
Jira worklogs are anonymized - they aren't attributed to individuals, don't contain Tempo {time record | worklog} descriptions, and don't contain additional information, such as Work Attributes.
Worklog updated in Jira | Worklog updated in Tempo | |
Time logged in Jira |
|
|
Time logged in Tempo |
|
|
