...
...
...
...
...
...
...
...
| align | left |
|---|---|
| class | content-box |
Table of contents
| Table of Contents |
|---|
| Info |
|---|
Synchronization with Tempo Apps is a BigPicture Enterprise feature and is currently available to Jira Server and Data Center users.on:
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.
| Info |
|---|
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).
| Info |
|---|
The same rule applies to our Holiday Plans. |
| Info |
|---|
Synchronization performed on the Workload Plan page will ONLY perform full sync of Workload Plans / Schemes, leaving Holiday Plans and Resources untouched for further synchronization on pages dedicated to these records (modules). |
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 decide to 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
BPBigPicture, which are only visible in
BPBigPicture), 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 |
|
Type of Action Performed in |
|---|
BigPicture | What will happen with the 'external’ Workload Plans (ones which were pulled from Tempo)? |
|---|---|
Adding native Workload/Holiday Plan |
|
Adding external Workload/Holiday Plan |
|
Modifying native Workload/Holiday Plan |
|
Modifying external Workload/Holiday Plan |
Warning: It is possible to switch the "overwritten" Plan back to its 'synchronized’ state by clicking the 'Re-synchronize with Tempo’ button in the detailed view of that specific W/H plan. |
Deleting native Workload/Holiday Plan |
|
Deleting external Workload/Holiday Plan |
- Workload/Ho
.
Automatic synchronization
You can set automatic synchronization with Tempo and define items to synchronize.
Go to BigPicture > App configuration > Integrations > Tempo.
Enable the Automatic Tempo Synchronization toggle switch.
Check items to synchronize automatically.
Define synchronization time.
Click Save.
...
How does Resource synchronization work?
Which Resource attributes are synchronized with Tempo? When synchronizing Resources,
...
BigPicture synchronizes Workload and Holiday Plans.
...
Regarding other attributes (name, surname, avatar, etc.), those are being pulled directly from
...
Jira, as both
...
BigPicture and Tempo are
...
Jira plugins and use the same pool of information.
...
Resource synchronization rules
Rules
...
that apply to Resource synchronization are a bit different from the rules of Workload and Holiday Plans Synchronization. Still,
...
the differences are
...
subtle since, as we’ve already mentioned, both plugins use Resource data, which is predefined in the user base in
...
Jira, and both pool the same data. This means that for both
...
Tempo and
...
BigPicture we are capable of finding the
...
Jira user which represents the same Resource.
Below
...
is a table that
...
summarizes and describes the rules of Resource synchronization. Those
...
that differ in Workload and Holiday Plan synchronization from Resource synchronization are marked with a blue color.
It is worth mentioning that as Resources are dependent on W&H Plans, the BigPicture performs the implicit synchronization of Workload and Holiday Plans during a Resource synchronization.
Action performed in Tempo | What will happen with the |
|---|
data in |
|---|
BigPicture during the synchronization? | |
|---|---|
Adding a Resource |
|
|
|
|
| |
Resource Modification |
|
Deleting Resource |
|
Action performed in BigPicture | What will happen with the external Resource (coming from Tempo)? |
|---|---|
Adding a new Resource |
|
Adding an external Resource |
|
Modifying a native Resource |
|
Modifying an external Resource |
Warning: It is possible to switch ‚overwritten’ Resource back to its ‚synchronized’ state by clicking the ‚Resynchronize with Tempo’ button in the detailed view of that specific Resource. |
Deleting a native Resource |
|
Deleting an external Resource |
|
Questions and answers
If I decide to overwrite a Workload/Holiday Plan, will that automatically overwrite Resources linked to that Workload/Holiday Plan?
You are probably wondering how would BigPicture act in a case when:
You’ve synchronized Workload Plan, Holiday Plans, and Resources with Tempo which creates dependency in which in
...
BigPicture you have synchronized Resources
...
that are assigned to synchronized Workload and Holiday Plans.
You’ve modified in
...
BigPicture one of the synchronized Workload Plans (or Holiday Plans) which made it become "overwritten".
Will that make Resources (which are linked to it) ‚overwritten’ too?
The answer is: "No." Changing the status of W/H Plans from synchronized to overwritten will not affect the Resources assigned to them. Then, It is possible
...
to have a synchronized Resource
...
assigned to an overwritten Workload / Holiday Plan.
How does the Team synchronization work?
Team names are used used.
The following Team Tempo attributes are synced:
Team Name
Team Summary
Team Members who are Jira users (including Team Members added via Jira groups). A Team Member is synchronized with all its Memberships, including:
Joining Date
Leaving Date
Skill
Availability
The
...
following
...
team Tempo
...
attributes
...
are
...
NOT
...
synchronized:
Team Mission Team Lead (a user who is the team leader)
Team Program (Program in Tempo is a group of Teams; each Team Tempo can belong to a maximum of 1 such group)
Team Members who are not Jira users (Tempo allows you to add such "virtual" Members)
Permissions Links to Boards and Projects
| Info |
|---|
During Team Synchronization, all Skills with Tempo are also synchronized, and missing Resources are also created (as NATIVE). |
Reconnect Tempo and BigPicture
To re-establish the Tempo connection with BigPicture:
Navigate to Tempo > Settings > OAuth 2.0 Applications.
Find BigPicture and select Delete.
Click the New Application button and add BigPicture.
Navigate to BigPicture > App Configuration > Integrations > Tempo.
Enter the credentials and press Save.