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 |
|
Adding an external Resource |
|
Modifying a native Resource |
|
Modifying an external Resource | • If the Resource is synchronized, then changes will be applied, and the Resource will change its status to ‚overwritten’. 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 |
|
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 case when:
- 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.
- 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.
