Jama Connect User Guide

When to use reuse and synchronize

Typical scenarios for reuse and synchronize include creating a library or catalog, branching, and release management.

  • Duplicate — You can make a copy of an item, container, or project. Synchronization is optional but can be enabled between items.

  • Library/Catalog — 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 must 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 you're 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.

  • Shared requirements — Large projects typically adhere to a common set of requirements, but often each requirement also has information specific to a project and must be managed by that project. For instance, a requirement name and description can be shared across multiple projects but release values, priorities, assignments, and relationships can continue to be managed by each project.

  • Branching — 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. In this case, reuse results in the versioning of an entire document made up of multiple items, rather than just a version of a single requirement.

  • Release management — Similar to branching, reuse and synchronization lets you use items across multiple releases or sprints in parallel.

  • Project template — 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.