...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Excerpt | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data storage and synchronizationIn order to be able to provide high performance and fast response times in the Timetracker Application, we synchronize the work logs from your Jira Cloud Instance to our servers. We do a full synchronization of worklogs when the application is installed and keep the two systems consistent afterward with regular incremental synchronization tasks. Jira will be always the “source of truth” regarding the worklogs. This means, that every time when a user log, edit or delete a worklog in our app, it will always save these changes in Jira first, and then it will synchronize these changes to our database. Our app does this with listeners and webhooks, so it will always catch worklog related events and synch these changes to our database real time, to keep the database up to date. (However, you can always trigger a synchronization manually as well.) With the synchronization:
Stored Worklog Data
Location and environment
Data removal and data retention
|