Working-Sets
Introduction
A component usually consists of dozens of specifications such as Requirements Specifications, Test Specifications, Design Specifications and others managed in multiple Codebeamer trackers. For each of the trackers, the correct version or variant must be selected to produce a consistent component. Users mostly work in the context of a component and are interested only in specific versions relevant in that context. With a large number of specifications involved in a complex project, it could be difficult to deal with different versions and variants of specifications.
Working-Sets enable the grouping of different specification versions and provide a context to work in for the user.
The main concepts of Working-Sets are:
• Working-Set: Working-Sets are defined in a specific project and include trackers at a defined version for each selected tracker. By combining different versions of trackers it is possible to define a Working-Set.
• Included tracker: A copy of a tracker that was branched from the original tracker at a point in time. After creating a Working-Set, two copies of the tracker exist and these copies can be modified independently of each other.
• Shared tracker: The selected tracker is included in the Working-Set, but not branched. After creating the Working-Set the tracker is shared between the original Working-Set and the new Working-Set. The tracker can be modified, but it is visible in both Working-Sets. A tracker can be shared in multiple Working-Sets.
• Excluded tracker: Trackers are excluded when they are not part of the Working-Set. External trackers are available in the context of the Working-Set.
• Default Working-Set: In every project, there is a predefined Default Working-Set that contains the Master branch of all trackers in the project.
• Merge: The process in which the changes from one branch are applied to its original one. During the merge process, the user has the ability to select the changes to be copied to the target branch. After the merge, the branches can still be modified independently of each other.
• Working-Set hierarchy: Working-Sets can also be derived from existing Working-Sets. This is the same process as creating a Working-Set from a Default Working-Set (Master branch) but instead of including, sharing, or excluding trackers from the default Working-Set, they originate from the selected Working-Set.
• Non-brancheable trackers: These trackers cannot be included in a Working-Set, and can only be shared or excluded. Non-brancheable trackers are test run, release, team, platform, test configuration, work log, issue, contact, bug, and document.
For more information on the high-level use cases supported by Working-Sets see: Working-Set Use Cases.
License and Permissions
 |
A branching license is required to use the Working-Set feature.
|
Your license must include the Working-Set option to access the Working-Set feature. Codebeamer has two Working-Set-related project permissions:
• Working-Set - View: Allows users to view Working-Sets.
• Working-Set - Admin: Allows users to administer Working-Sets. Users with this permission can create and merge Working-Sets.
 |
Users with the Working-Set - Admin permission can configure the trackers in the Working-Sets they create.
|