Tempo synchronization
Table of contents
Synchronization with Tempo Apps is a BigPicture Enterprise feature and is currently available on:
Jira Server
Jira Data Center
Jira Cloud (BigPicture version 8.2 (21 Oct 2021) or higher)
Synchronization will only work if plugins are installed within the same instance of the Jira environment (this applies for Jira Server as well as Jira Data Center).
More information on the differences between cloud and server versions of the App can be found here.
To synchronize with Tempo Apps, make sure to have one of the following installed:
Tempo Timesheets for Jira v. 7.9 (released on 2014-05-05) and later,
Tempo Planner for Jira v. 1.3 (released on 2014-06-11) and later,
Tempo Budgets for Jira v. 8.0 (released on 2015-05-01) and later.
What features can be synchronized?
The "Synchronize with Tempo" buttons trigger the synchronization between BigPicture Enterprise and the Tempo plugin of your choice.
It is important to bear in mind that a user 'triggers' the synch-up - the synchronization between our plugin and Tempo plugins can be achieved only at the user’s request.
Feature | Synchronized with Tempo? |
---|---|
Workload Plans | Yes (Tempo name used: Workload Schemes) |
Holiday Plans | Yes (Tempo name used: Holiday Schemes) |
Teams and team members | Yes |
Skills | Yes (Tempo name used: Roles) |
Resources | All of the above will be synchronized. |
Workload and Holiday Plans synchronization
The Workload Schemes which were imported from the Tempo plugin can be distinguished by:
Tempo label,
Tempo code.
Codes of these external Workload Plans were automatically generated to describe the external (Tempo's) WP's. These codes also have Tempo attached to their name, so you cannot mistake them for our native codes.
You might have also noticed that before the synchronization in BigPicture and in the Tempo plugin there were two workload patterns recorded under the same name: a Workload Plan and a Workload Scheme named „Full-time”, then after we proceeded with the synchronization of a Workload Scheme - a new „Full-time” Workload Plan was generated. As a result, we have two Workload Plans named: „Full-time” of which one is native, and one is external. This decision was made to avoid unwanted mistakes and make our project safer. This is why we do not merge any objects and do NOT alter any data or information in any of your Workload records (even if they carry the same name).
The same rule applies to our Holiday Plans.
Plans updated using Tempo
One-way sync at request if provided by the app.
Will the plans in Tempo be synchronized to reflect BigPicture? The answer is: "No, they won’t”. And it is not an error - it is indeed a feature. A feature that intends to give a user as much control over a project as possible. For the External Workload/Holiday plans to be synchronized correctly after changes were implemented in Tempo Schemes, you will have to use the "Synchronize with Tempo” button. This sort of behavior may seem far from intuitive, though (as we’ve mentioned) it is intended to give you as much control over the data flow between both plugins as possible.
Plans updated using BigPicture
What will happen if you modify the synchronized Workload/Holiday Plan in BigPicture? Plans will be overwritten and a "pen" icon will be added to the label.
Deleting plans
What will happen when we delete from Tempo Workload/Holiday Scheme synchronized with BigPicture? It depends if the object you deleted was ‚synchronized’ or "overwritten".
If the object is marked as 'synchronized', then during the Synchronization with Tempo it will also be deleted from BigPicture.
If the object is marked as 'overwritten' (which means you’ve implemented some changes from the perspective of BigPicture, which are only visible in BigPicture), then during the next synchronization with Tempo, it WILL NOT be deleted and will become a 'native’ object.
Synchronization rules
The synchronization rules are summed up in the table below:
Type of Action Performed in Tempo | What will happen during Synchronization in BigPicture |
---|---|
Adding Workload/Holiday Scheme |
Warning: An external Workload/Holiday Plan will be generated even if a native W/H Plan is already in place in BigPicture (with the same name and/or the same daily workloads). |
Modifying Workload/Holiday Scheme |
|
Deleting Workload/Holiday Scheme |
|