Why would an organization utilize Reuse & Sync?
You can make a copy of an item, container or project. Synchronization is optional but can be enabled between items.
Create a library or catalog to establish system-wide standards in your organization for all business units to follow. These might include common business practices, rules, glossaries or even a set of non-functional requirements that teams should reference but not modify.
For example a business that relies heavily on acronyms and terminology might create a glossary that can be defined and managed in one place, and used as a reference everywhere else. Another organization might create and manage business practices in one place, allowing references to those practices to remain consistent across the organization. TIP: If are using a catalog to push changes to many projects, you can synchronize items to push changes from your “catalog” project to all other project items that share the same global ID. You must have write access on all projects in the sync to do this.
Large projects typically adhere to a common set of requirements, but often each requirement also has information specific to a project and needs to be managed by that project. For instance, a re- quirement name and description can be shared across multiple projects but release values, priorities, assignments, and relationships can continue to be managed by each project.
With branching you can split a set of information from a single point in time into several branches such that each branch can be modified in parallel.
This can be useful when you want a snapshot of items at a particular point in time, but to still allow these items to be modified in parallel. Reuse in this case results in the versioning of an entire docu- ment made up of multiple items, rather than just a version of a single requirement.
Similar to branching, reuse and synchronization lets you use items across multiple releases or sprints in parallel.
You can set up a project to act as a template that you reuse and synchronize to quickly ramp up new projects or to establish standard practices on content organization. You can also synchronize the template to push updates to associated projects.
What is the difference between reuse and project duplication? What about item duplication?
What are "sync options"?
Sync options allow you to create and apply rules for how synchronization should work. This includes the option to synchronize relationships or widgets of an item.
There are also advanced sync options that allow users to apply reuse rules in a target location. Example: When synchronizing requirements, also synchronize only the downstream defects.
How do I see which items are synced?
In the explorer tree, a blue dot will show in the bottom right-hand corner of the synchronized items.
You can then see whether the items are in- or out-of-sync from the single item view synchronization widget or the sync items wizard. You can compare synced projects, components, sets, folders and items from there too.
How do I prevent users from synchronizing items?
Users can only make changes to items they have to Write permissions to. They cannot modify items through synchronization that have a user lock or a system lock, either.
As soon as you have Read permissions you can reuse an item. Reuse is actually only restricted on the destination where users need Create/Edit permissions. This means there's no way to restrict reuse unless you restrict access to the project, which can be done by granting each projects' permissions at the project level.
Locked or System Locked items cannot be modified through synchronization.
Can I prevent an item in my project from being updated via synchronization?
Locked and System locked items cannot be modified through synchronization.
What happens to a synchronized item when I convert it to another item type?
When you convert a synchronized item to different item type, such as converting a Requirement to a Feature Request, the item will lose its synchronization and will receive a new Global ID.
Can I synchronize containers?
Yes. You can synchronize projects, components, sets, folders, or items.
If you Reuse items into a new container, the items would inherit permissions from the destination. The caveat to this is reusing containers (e.g. a folder with items inside). When containers (folders, sets, components) are reused, they will retain their original permissions regardless of the permissions set inside the destination.
What does the "Reuse source project hierarchy in destination project" in reuse mean?
You can select this option as part of the reuse process.
This option will reuse all of the hierarchy of the source project selection (including components, sets, and folders) and copy that over to the destination project.
Why can't I see the upstream item in the Sync items Wizard?
Synchronized items will share the same Global ID and no single item is marked or identified as the upstream (the original or parent item) or downstream. This allows for more flexibility and scalability in synchronization.
Do Synchronization updates trigger Suspect Links?
When an item type is updated by an org administrator to enable Sync on a field, what does that do?
Whenever the Reuse and Sync feature is used for that item type in any project, that field will be copied and any future changes will be flagged as “out of sync” from the original item.
What is a Global ID and what is its role in reuse?
The Global ID is a universal identifier. This is used for linking items together so that they can be compared and synchronized. You can read more about how the Global ID is used in reuse here.
If I break the sync will the Global ID change?
Yes. As soon as you break the synchronization between two items, each one will have its own Global ID.
Can I save a comparison view of the synced items?
Yes, you can configure a comparison view and save the view.
What is the little blue dot on items in my tree?
The blue dot is a quick visual indicator that shows which items, folders, sets, and components have been synchronized.
Can I synchronize from one to many (projects or items)?
Yes. You can synchronize item by item or use the Sync All functionality in the Sync Items window. However, if you need to view and sync the items, you will have to initiate one-to-one synchronizations.
Can I synchronize widgets?
Yes. You can synchronize the most relevant widgets including tags, links, and attachment links. However, synchronization for widgets needs to be enabled by the administrator on each item type, under Admin > Item Types > Edit.
What is a reuse rule?
A reuse rule allows you to reuse not only specific items but also items related to your primary selection.
Example: copy a requirement and all of its downstream test cases but not the downstream bugs.
You can also select specific fields to be copied to the new item as opposed to the default settings (all fields set to sync).
Can rules be applied to all projects?
All rules created within the organization are available to all projects under the advanced reuse options view, even when the user has no permissions on the project where the rule was originally created.
Rules that are not applicable in another project will be hidden by default, nevertheless, they can be made visible by the users and selected from any project.
Can rules be created only to specific projects?
You cannot restrict reuse rules to other projects. Rule names can be used to clearly describe the project for which each rule is intended.
Also, rules need to be selected by the users in order to be applied.
Can I grant reuse advanced rule access to a project manager but limit access to other projects?
Yes. For this, you need to grant the required Reuse Administrator permissions at the org level (but only this specific permission at that level).
Additionally, you need to grant the project manager the Manage Project permissions at the corresponding project's level.