Reuse
If your projects contain items that are often the same or slightly different, reusing items helps you work more efficiently. You can reuse items over multiple projects and synchronize them, as needed.
Reuse for users
Selecting items to reuse can be helpful if you are creating several copies, but want the original “source” item to maintain a connection with its copied items.
For example, you might have a set of requirements from a library project in Jama Connect and need to reuse it in several other projects. You copy the set to Project 1 and Project 2. When viewing the copied requirements in Project 2, users might see an upstream relationship to the “source” requirements in the library. Adding or not adding this relationship has no impact on how items are compared or synced.
You can only reuse items in sets of the same item type. For example, if you have two requirement sets in a project created from the same item type, you can duplicate and move items between these sets. Child items can also be reused, but they must be the same item type as the parent item.
Tip
If you have several items that are reused regularly, put them in a central project so future changes to items can be maintained from a central location. For instance, during reuse, relationships can automatically be created that are inconsistent with the relationship rules of a specific project.
Reuse administration
Reuse is best managed by a dedicated reuse admin. An organization admin can assign reuse admin permissions.
Reuse admins are the only ones who can:
Edit and delete Compare Views of synchronized items.
Manage (add, edit, delete) reuse rules under Advanced options.