NAVIGATION
Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

This groundbreaking feature allows you to synchronize your Workload Plans, Holiday Plans, Resources and Teams with their counterparts in the Tempo app of your choice! As a result of this integration, the BigPicture will allow you to access objects in your Tempo add-ons. The purpose of this article is to get into detail on how this synch-up works and how it can be used.

Tempo Apps Which Synchronize With BigPicture

Synchronization with Tempo was added to BP Enterprise with version 2.1.0. Starting with this release, BP can now integrate with any plugin mentioned below: 

  • Tempo Timesheets for JIRA v. 7.9 and above
  • Tempo Planner for JIRA v. 1.3 and above
  • Tempo Budgets for JIRA v. 8.0 and above

Synchronization between BPE and Tempo plugins will only work if plugins are installed within the same instance of Jira environment (this applies for Jira Server as well as Jira Data Center)

What features can be synchronized?

For the time being the synchronization allows BigPicture to manage Workload Plans ( a.k.a Workload Schemes in Tempo ), Holiday Plans ( Tempo’s Holiday Schemes ), and Resources. In the near future we are planning to add synchronization between Teams and their Members, so please stay tuned!

On the following BP pages: Workload Plans, Holiday Plans and Resource Manager you may now find „Synchronize with Tempo” button. This button allows you to trigger the synchronization between BigPicture Enterprise and 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 now be achieved only on user’s request. It has to be ‚triggered’ manually. Automatic synchronization has not yet been implemented, yet we are planning to add it very soon.

With the new synchronization scheme, there’s a set of rules that has to be applied. To make it easier for you to understand all of them we will explain them with examples of use-cases. As these rules apply likewise to both: Workload and Holiday Plans we will explain them in one chapter. Rules of the Resource module synchronization will be mentioned in a separate chapter.

How does the Workload and Holiday Plans synchronization work?

On the screenshots above we can see a list of BigPicture’s Workload Plans (left) and list of Tempo’s Workload Schemes (right). In the BP no Workload Scheme can be seen, as we have not synchronized them yet.

Next graphics show what would happen after pressing „Synchronize with Tempo” button visible in the top-right corner of our plugin.

You've probably already noticed that in the Workload Plans which were imported from Tempo plugin - the Tempo name is now displayed. This way we can distinguish BigPicture’s native Workload Plans from the ones which were pulled from Tempo - external ones. 

Also codes of these external Workload Plans were automatically generated in order 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 if before the synchronization in BP 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 proceed 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 in order to avoid any unwanted mistakes and keep our project safer. This is why we do not merge any objects and do not alter any data nor information in any of your Workload records (even if they carry the same name).  

[The same rule applies to our Holiday Plans. As we’ve already mentioned both Plan types go under the same set of rules].

It is also good to note that by clicking „Synchronize with Tempo” executes a full sync-up all Tempo’s Workload Plans, meaning that it is collective. Please remember though, that synchronization performed on the Workload Plan page will ONLY perform a full sync of Workload Plans / Schemes, leaving Holiday Plans and Resources untouched for further synchronization on pages dedicated to these records (modules).   

What will happen when we decide to modify Workload / Holiday Plan which has already been synchronized with BP directly from Tempo?

Will these changes be directly reflected in the BigPicture plugin? 

The answer is: „No, they won’t”. And it is not and error - it is indeed a feature. A feature which intends to give a user as much control over a project, as it is possible. In order 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 behaviour may seem to be far from intuitive, though (as we’ve mentioned) it is intended in order to give you as much control over the data-flow between both plugins as it is possible. Nevertheless, we are planning to implement automatic synchronization between Tempo and BP in future. The feature naturally will allow you to decide if you’d wish for the automatic sync-up to take place or not.

As we can see on the picture above - we’ve modified one of Workload Schemes, adding „(40 hours)” part to its name.

As you can see, the change is not reflected in BigPicture. It will only appear after clicking on the „Synchronize with Tempo” button. [as seen on the picture below].


Naturally, not only Scheme Names are synchronized. Most importantly, it is daily workloads of each Workload Scheme that follow the synchronization. (Same goes for the synchronization of Holiday Plans - names as well as all fixed and floating holidays are synchronized in this case).

What will happen if you decide to modify synchronized Workload/Holiday Plan in BigPicture?

Is it even possible? Well… It is indeed, though any changes made in BigPicture will not be ever reflected in Tempo (as for now), since the „Synchronize with Tempo” button is only present in BP. Such a ‚sync-up’ button is not present in Tempo plugin, therefore we will not be able to migrate changes in our record into Tempo’s Workload Scheme. 

We may modify anything we want in BigPicture, though these changes will only be reflected in our PPM plugin. This of course brings us up to the following conclussion: that the Synchronization with Tempo plugin works only in a one direction. BP is capable of reading objects in Tempo and pulling them into its own structure, though it is not capable of transferring changes back to Tempo plugin. 

What is also very significant, is the fact that right after you modify and external object, which was beforehand synchronized with Tempo, it stops being ‚synchronized’ and becomes an ‚overwritten’ object. Let’s see an example in which we modify "Half-time" Workload Plan by changing its daily workloads. This is how this Workload Plan is now shown on the list:

As you can see on the screenshot above, our modification resulted in the immediate addition to the name of this Workload Plan - the „OVERWRITTEN” banner. 

What does that mean? It means that from now on whenever synchronizing Workload Plans with Tempo, BP will ignore changes which we’ve made in Tempo in that specific Workload Scheme, in order for user not to lose changes made from the BP perspective. [same goes for Holiday Plans] 

What will happen when we decide to delete from Tempo Workload/Holiday Scheme which is synchronized with BP? It really depends if the object which you’ve deleted was either ‚synchronized’ or ‚ovewritten’.

  • 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 BP, which are only visible in BP), then during the following Synchronization with Tempo it WILL NOT be deleted and will become a ‚native’ object.

Below screenshots may shed some more light over the above statement:

On the picture above we've presented two external Workload Plans. One of which is synchronized and one is overwritten. Let's have a look what will happen if we delete both corresponding schemes in the Tempo, and press the "Synchronize with Tempo":

Just as we expected, the synchronized "Full-time (40 hours)" Workload Plan was automatically deleted and the overwritten "Half-time" Workload Plan has become native. What would happen if we've deleted an external Workload Plan which is pulled from Tempo? Well... The answer to this is: "This is not possible, such action is prohibited." You may have already noticed that for external Workload Plans their corresponding "Delete" buttons are simply disabled: 

It isn't crucial if such an external object is 'synchronized' or 'overwritten'. It really matters that it is 'external' and BP will prevent it from being deleted. If we want it to be deleted, we need to purge it from its native environment (which in this case is Tempo).

Is it possible for the overwritten Workload / Holiday Plan to become synchronized once again? It is indeed! In order to do that, please go to overwritten Workload Plan’s details and at the top of the page you will see: „Resynchronize with Tempo” button. This button forces the plugin to once again synchronize the Workload Plan with its Tempo counterpart.

Workload and Holiday Plans synchronization rules

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/Holdiay Plan will be generated even if a native W/H Plan is already in place in BP (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 BP

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 added as a ‚native’ one.

Adding external Workload/Holiday Plan

•  Such 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 overwitten, then changes will be applied without a status change.


Warning: It is possible to switch ‚overwritten’ Plan back to its ‚synchronized’ state by clicking the ‚Resynchronize with Tempo’ button in detailed view of that specific W/H.

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

  • The plugin will prevent you from performing this action. 

It is only possible by deleting the Plan from Tempo plugin!


How does the Resource synchronization work?

Which Resource attributes are synchronized with Tempo? When synchronizing Resources, what BigPicture does is really synchronization of Resources in Workload and Holiday Plans. When it comes to Resource’s other attributes (name, surname, avatar etc.), those are being pulled directly from JIRA as both: BP and Tempo are JIRA plugins and use the same pool of information.

Resource synchronization rules

Rules which apply to Resource synchronization are a bit different from rules of Workload and Holiday Plans Synhronization, but differences are really 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 BP we are capable of finding the JIRA user which represents the same Resource. Below you can find a table which sums up and describes rules of Resource synhronization. Those which differ Workload an Holiday Plan synchronization from Resource synchronizarion are marked with a blue colour. 

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 BP during the synchronization?

Adding a Resource

If in BP the Resource already exists for the same user in JIRA, the 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 BP the Resource does not exist for the same 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 is overwritten, then changes will be ignored.

Deleting Resource

The corresponding Resource changes its status to ‚native’ (regardles 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 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 detailed view of that specific Resource.

Deleting a native Resource

  • This operation cannot be performed

Deleting an external Resource

  • This operation cannot be performed

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 case when: 

  1. You’ve synchronized Workload Plan, Holiday Plans and Resources with Tempo which creates dependency in which in BP you have synchronized Resources which are assigned to synchronized Workload and Holiday Plans. 
  2. You’ve modified in BP one of synchronized Workload Plans (or Holiday Plans) which made it to become ‚overwritten’. 

Will that make Resources (which are linked to it) ‚overwritten’ too? 

The answer is: "No." Changing status of W/H Plans from synchronized to overwritten will not affect Resources assigned to them. It is possible then to have synchronized Resource that is assigned to overwritten Workload / Holiday Plan.


 

Jak działa synchronizacja Skilli?

Najważniejsza informacje:

  • To, co w BP nazywamy Skillami, w Tempo nazywa się Role.
  • Skille są synchronizowane po nazwie.
    • Przykład: Jesteśmy przed pierwszą synchronizacją BP-Tempo. W BP jest Skill o nazwie "Developer", w Tempo jest Role o nazwie "Developer". Podczas synchronizacji Skill "Developer" z BP (do tej pory NATIVE) stanie się SYNCHRONIZED z Role "Developer" z Tempo.
    • (Szczegółowe informacje dot. synchronizaowania po nazwie są w tabeli poniżej.)


Akcja wykonana w Tempo

Co się stanie podczas synchronizacji z danymi w BP?

Dodanie Skilla

  • Jeżeli w BP istnieje NATIVE Skill o takiej samej nazwie, jaką ma Skill dodany do Tempo, to Skill w BP stanie się SYNCHRONIZED, a jego stan (tj. nazwa i opis) zostanie zsynchronizowany ze stanem Skilla w Tempo
  • W przeciwnym przypadku, w BP zostanie utworzony nowy EXTERNAL SYNCHRONIZED Skill na podstawie Skilla z Tempo

Modyfikacja Skilla

  • Jeżeli odpowiadający Skill jest SYNCHRONIZED, to nastąpi synchronizacja zmian

  • Jeżeli odpowiadający Skill jest OVERWRITTEN, to zmiany zostaną zignorowane

Usunięcie Skilla

  • Odpowiadający Skill zmieni status na NATIVE (niezależnie od tego, czy był SYNCHRONIZED, czy OVERWRITTEN)

Akcja wykonana w BP

Co się stanie ze Skillami EXTERNAL (czyli pochodzącymi z Tempo)?

Dodanie NATIVE Skilla

-

(Nic się nie stanie z EXTERNAL Skillami. Skill zostanie po prostu dodany jako NATIVE.)

Dodanie EXTERNAL Skilla

-

(Brak takiej operacji. Z poziomu BP można dodawać tylko NATIVE Skille. EXTERNAL Skille powstają wyłącznie w efekcie synchronizacji z Tempo.)

Modyfikacja NATIVE Skilla

-

(Nic się nie stanie z EXTERNAL Skillami. Skill zostanie zmodyfikowany i nadal będzie miał status NATIVE).

Modyfikacja EXTERNAL Skilla

  • Jeżeli Skill jest SYNCHRONIZED, to zmiany zostaną dokonane, a Skill zmieni status na OVERWRITTEN

  • Jeżeli Skill jest OVERWRITTEN, to zmiany zostaną dokonane (bez zmiany statusu)

Uwaga: Jest możliwe, aby OVERWRITTEN Skill stał się z powrotem SYNCHRONIZED. W tym celu wystarczy dla tego Skilla kliknąć przycisk "Resynchronize with Tempo".

Usunięcie NATIVE Skilla

-

(Nic się nie stanie z EXTERNAL Skillami. Skill zostanie po prostu usunięty.)

Usunięcie EXTERNAL Skilla

-

(Operacja niedozwolona. Usunięcie EXTERNAL Skilla jest możliwe tylko po uprzednim usunięciu jego odpowiednika z Tempo.)


Jak działa synchronizacja Teamów?

Najważniejsze informacje:

  • BP synchronizuje Teamy z Tempo jako Globalne Teamy.
    • Czyli jeżeli chce się, aby Team z Tempo można było użyć w kontekście jakiegoś Programu, to należy przeprowadzić synchronizację (która utworzy Team Globalny), a następnie przejść do Teamów w interesującym nas w Programie w BP, po czym wybrać opcję "Use global team".
      • Można też wybrać opcję "Create copy of global team", która utworzy kopię Globalnego Teamu zsynchronizowanego z Tempo. Niestety, ponieważ będzie to kopia, kolejne synchronizacje z Tempo nie będą jej aktualizować (aktualizowany będzie tylko Globalny Team).
  • Teamy NIE są synchronizowane po nazwie.
    • Czyli jeśli w BP będzie istniał Globalny Team o nazwie "Witches" i w Tempo będzie istniał Team o nazwie "Witches", to podczas synchronizacji BP utworzy drugi Globalny Team o nazwie "WItches", synchronizowany z odpowiednikiem z Tempo.
  • Następujące atrybuty Teamów Tempo są synchronizowane:
    • Team Name
    • Team Summary
    • Team Members, którzy są użytkownikami Jiry (łącznie z Team Memberami dodanymi poprzez grupy z Jiry)
    • Dla każdego ww. Team Member synchronizowane są wszystkie jego Membershipy, a w każdym z nich:
      • Joining Date
      • Leaving Date
      • Skill
      • Availability
  • Następujące atrybuty Teamów Tempo NIE są synchronizowane:
    • Team Mission
    • Team Lead (użytkownik, który jest liderem Teamu)
    • Team Program (Program w Tempo to grupa Teamów; każdy Team Tempo może należeć do maksymalnie 1 takiej grupy)
    • Team Members, którzy nie są użytkownikami Jiry (Tempo pozwala dodawać takich "wirtualnych" Memberów)
    • Permissions
    • Links to Boards and Projects
  • Podczas synchronizacji Teamów synchronizowane są także wszystkie Skille z Tempo, a także tworzone są brakujące Resource'y (jako NATIVE).


Akcja wykonana w Tempo

Co się stanie podczas synchronizacji z danymi w BP?

Dodanie Teamu

  • Utworzenie EXTERNAL SYNCHRONIZED globalnego Teamu na podstawie danych z Tempo

    • Uwaga: Nowy EXTERNAL SYNCHRONIZED Team powstanie zawsze – nawet jeśli w BP istnieje już NATIVE Team o identycznej nazwie co Team z Tempo

Modyfikacja Teamu

  • Jeżeli odpowiadający Team jest SYNCHRONIZED, to nastąpi synchronizacja zmian

  • Jeżeli odpowiadający Team jest OVERWRITTEN, to zmiany zostaną zignorowane

Usunięcie Teamu

  • Jeżeli odpowiadający Team jest SYNCHRONIZED, to nastąpi usunięcie Teamu
  • Jeżeli odpowiadający Team jest OVERWRITTEN, to status Teamu zostanie zmieniony na NATIVE

Akcja wykonana w BP

Co się stanie z EXTERNAL Teamami (czyli pochodzącymi z Tempo)?

Dodanie NATIVE Teamu

-

(Nic się nie stanie z EXTERNAL Teamami. Team zostanie po prostu dodany jako NATIVE.)

Dodanie EXTERNAL Teamu

-

(Brak takiej operacji. Z poziomu BP można dodawać tylko NATIVE Teamy. EXTERNAL Teamy powstają wyłącznie w efekcie synchronizacji z Tempo.)

Modyfikacja NATIVE Teamu

-

(Nic się nie stanie z EXTERNAL Teamami. Team zostanie zmodyfikowany i nadal będzie miał status NATIVE).

Modyfikacja EXTERNAL Teamu

  • Jeżeli Team jest SYNCHRONIZED, to zmiany zostaną dokonane, a Team zmieni status na OVERWRITTEN
  • Jeżeli Team jest OVERWRITTEN, to zmiany zostaną dokonane (bez zmiany statusu)

Uwaga: Jest możliwe, aby OVERWRITTEN Team stał się z powrotem SYNCHRONIZED. W tym celu wystarczy dla tego Teamu kliknąć przycisk "Resynchronize with Tempo".

Usunięcie NATIVE Teamu

-

(Nic się nie stanie z EXTERNAL Teamami. Team zostanie po prostu usunięty.)

Usunięcie EXTERNAL Teamu

-

(Operacja niedozwolona. Usunięcie EXTERNAL Teamu jest możliwe tylko po uprzednim usunięciu jego odpowiednika z Tempo.)


Wydajność synchronizacji z Tempo

Mechanizm synchronizujący BP z pluginami Tempo został przez nas kompleksowo przetestowany pod względem wydajności. Powiemy krótko: synchronizacja z pluginami Tempo rocks także pod względem wydajności.

Inicjalna synchronizacja BP z Tempo, w którym zdefiniowano 2 500 Teamów (ze średnio 10 Memberami każdy, a każdy Member ze średnio 3 Membershipami), 20 000 Resource'ów, 400 Role, 400 Workload Scheme i 400 Holiday Scheme zajmowała na naszych testowych maszynach średnio ok. 3 minut, natomiast każda kolejna synchronizacja - ok. 30 sekund (różnica w czasie bierze się z faktu, że podczas inicjalnej synchronizacji BP tworzy nowe dane, a podczas każdej kolejnej - tylko je aktualizuje). Jakie były parametry techniczne naszych testowych maszyn? Procesor 2,2 GHz Intel Core i7, pamięć RAM o pojemności 3 GB - a więc jak widać, nothing special. Aha, na testowej maszynie stała zarówno Jira, jak i baza danych.

Ponieważ większość z naszych Klientów nie dysponuje aż tak wielkimi wolumenami danych, zakładamy, że w większości przypadków synchronizacja wszystkich Teamów, Resource'ów etc. będzie trwała pojedyncze sekundy (no może z wyjątkiem inicjalnej, która może potrwać maksymalnie kilka minut).

HIGHLIGHTS

You are evaluating RefinedTheme.