Versions Compared

Old Version 4

changes.mady.by.user Anna Ciepłota

Saved on

compared with

New Version Current

changes.mady.by.user Magdalena Żaczek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of contents

...

Info

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 Jira v. 7.9 (released on 2014-05-05) and later,

  • Tempo Planner for JIRA Jira v. 1.3 (released on 2014-06-11) and later,

  • Tempo Budgets for JIRA Jira v. 8.0 (released on 2015-05-01) and later.

...

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 any unwanted mistakes and keep make our project safer. This is why we do not merge any objects and do not NOT alter any data or information in any of your Workload records (even if they carry the same name).  

...

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 is 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 to be 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 it is possible.

Plans updated using BigPicture

...

Deleting plans

What will happen when we decide to delete from Tempo Workload/Holiday Scheme which is synchronized with BigPicture? It depends if the object you’ve you deleted was either ‚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.

...

Type of Action Performed in Tempo

What will happen during Synchronization in BigPicture

Adding Workload/Holiday Scheme

  • Creation of a new - external Workload/HolidayPlan with the data stored in Tempo.

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

  • If corresponding Workload/Holiday Plan is synchronized, then all changes will be implemented.

  • If corresponding Workload/Holiday Plan is overwritten, then all changes will be ignored.

Deleting Workload/Holiday Scheme

  • If corresponding Workload/Holiday Plan is synchronized, then the Workload/Holiday Plan will be deleted.

  • If corresponding Workload/Holiday Plan is overwritten, then the status of that W/H Plan will be set to ‚native’.

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

  • Nothing will happen with the external Workload/Holiday Plan. The W/H Plan will just be added as a "native" one.

Adding external Workload/Holiday Plan

  • Such an operation cannot be performed. In BigPicture only native Workload/holiday Plans can be added and the external ones are generated only through the synchronization with Tempo.

Modifying native Workload/Holiday Plan

  • Nothing will happen with the external Workload/Holiday Plans. The W/H Plan will just be modified and stay in the native status.

Modifying external Workload/Holiday Plan

  • If Workload/Holiday Plan is synchronized, then changes will be applied and W/H Plan will change its status to 'overwritten’.

  • If Workload/Holiday Plan is overwritten, then changes will be applied without a status change.

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

  • Nothing will happen with the external Workload/Holiday Plans. The W/H Plan will just disappear.

Deleting external Workload/Holiday Plan

Workload/Ho
.

Automatic synchronization

You can set automatic synchronization with Tempo and define items to synchronize.

  1. Go to BigPicture > App configuration > Integrations > Tempo.

  2. Enable the Automatic Tempo Synchronization toggle switch.

  3. Check items to synchronize automatically.

  4. Define synchronization time.

  5. Click Save.

...

How does Resource synchronization work?

Which Resource attributes are synchronized with Tempo? When synchronizing Resources, BigPicture synchronizes Workload and Holiday Plans. When it comes to Regarding other attributes (name, surname, avatar, etc.), those are being pulled directly from JIRA Jira, as both : BigPicture and Tempo are JIRA Jira plugins and use the same pool of information.

...

Rules that apply to Resource synchronization are a bit different from the rules of Workload and Holiday Plans Synchronization. Still, but the differences are really subtle since, as we’ve already mentioned, both plugins use Resource data, which is predefined in the user base in JIRAJira, and both pool the same data. This means that for both : Tempo and BigPicture we are capable of finding the JIRA Jira user which represents the same Resource.
Below you can find is a table that sums up 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. 

...

Action performed in Tempo

What will happen with the data in BigPicture during the synchronization?

Adding a Resource

  • If in BigPicture the Resource already exists for the same user in JIRAJira, the Resource will become synchronized, and its status will become synchronized with its counterpart in Tempo, meaning the Resource will be assigned to the Workload and Holiday Plan which was predefined and assigned to in Tempo plugin.

  • If in BigPicture the Resource does not exist for the same JIRA Jira user, then with data pulled from Tempo, a new external synchronized Resource will be created.

Resource Modification 

  • If the corresponding Resource is synchronized, then changes will be synchronized.

  • If the corresponding Resource is overwritten, then changes will be ignored.

Deleting Resource

  • The corresponding Resource changes its status to 'native’ (regardless if it was synchronized or overwritten)

Action performed in BigPicture

What will happen with the external Resource (coming from Tempo)? 

Adding a new Resource

  • Nothing will happen with the external Resource. It will be added as a native one.

Adding an external Resource

  • This operation cannot be performed

Modifying a native Resource

  • Nothing will happen to external Resources. It will be modified and will still hold a ‚native’ status. 

Modifying an external Resource

  • If the Resource is synchronized, then changes will be applied, and the Resource will change its status to ‚overwritten’.

  • If the Resource is already ‚overwritten’ then changes will be applied without a status change.

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

  • This operation cannot be performed

Deleting an external Resource

  • This operation cannot be performed

...

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 then to have a synchronized Resource that is 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:

...

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:

  1. Navigate to Tempo > Settings > OAuth 2.0 Applications.

  2. Find BigPicture and select Delete.

    Image Added

  3. Click the New Application button and add BigPicture.

  4. Navigate to BigPicture > App Configuration > Integrations > Tempo.

  5. Enter the credentials and press Save.

    Image Added