Worklogs
Syncing Jira worklogs makes it easier to keep time-tracking data aligned across multiple Jira projects. This feature ensures that time logs remain consistent and accessible in all relevant projects for all teams.
Here, you can find a step-by-step guide on configuring worklog sync in Backbone. Below, You can read more about the different settings and functionalities, the deletion behavior, and how it works with Tempo.
Sync Worklogs
To synchronize worklogs, you have multiple options:
Anonymous - Backbone or the sync user adds the synced worklog - handy when the users are not the same on both instances
Enrichment - Backbone or the sync user adds the synced worklog, but you can add some additional information to the synced worklog
Anonymous
Worklogs will be added or edited by the synchronization user. Therefore, changes by different users in the partner project will appear as synchronization user changes.
Enrichment
If you would like to have more details about the actual author of the worklog, you can activate the enrichment by specifying a velocity template that will generate the worklog description. An enrichment must be enclosed by ${ ... } like in the default template. For enrichments, the following template variables are available:
Variable | Description |
|---|---|
| The actual content of the worklog. |
| The display name of the user who wrote the worklog. |
| The email address of the user who wrote the worklog. |
| The time when this worklog has been added |
| The time when this worklog was added, expressed with a custom date format. For a list of available date formatting options, see the Java docs |
| The display name of the user who edited the worklog. |
| The email address of the user who edited the worklog. |
| The time when this worklog has been edited. |
| The time when this worklog has been edited, expressed with a custom date format. For a list of available date formatting options, see the Java docs |
| The timezone in readable form (helpful when your partner project uses a different time zone than you). |
Deletion Behavior
If a worklog has been added in project A and later deleted in project A, the worklog will also be deleted in project B.
If a worklog has been added in project A and later deleted in project B, the worklog will not be deleted in project A. If this worklog is then edited in project A, it will be recreated in project B.
Whenever worklogs are edited in the project where they were created originally, the corresponding worklogs in the other project will be updated (overwritten).
Worklog Synchronization with Tempo
Each Tempo entry automatically creates a corresponding worklog entry. When synchronizing worklogs while using Tempo, the synchronization process applies to the worklog entries generated by Tempo rather than the original Tempo entry itself.