Creating Working-Sets
How to Create Working-Sets
 |
Working-Set creation runs in the background. This means that the created Working-Set is not available immediately, but you receive a notification email and a message in the browser when it is complete.
|
With the Working- Set - Admin project permission, you can create a Working-Set from two places:
1. Click the three dots of the Admin tab and select Create Working-Set:
2. In Trackers page and click the Working-Set icon.
This opens an editor dialog box like this:
The fields include:
• Name:(Required) The name of the Working-Set. Mandatory field.
• Color: (Optional) This color is used as the header color to make it more recognizable.
• Key postfix: (Optional) By default, it is empty. Will be used in the interwiki links of Working-Set items.
• Description: (Optional) Description for the Working-Set.
| | The name of the a Working-Set can also used as the name the baseline of the Working-Set For details refer to the baseline section. |
When done click Next (Select Trackers) to navigate to the trackers selections page:
Selecting trackers:
• Trackers are grouped into Work Items and Configuration items.
• By default, all available trackers are selected:
◦ Non-brancheables are selected as shared trackers.
◦ Other trackers are selected as included trackers.
• If the project has at least one baseline, then the baseline selection combo-boxes are available:
◦ The checkbox at the top sets the common baseline for the entire Working-Set.
◦ Each included tracker has one checkbox to set a tracker-specific baseline.
◦ By default 'HEAD' is selected for all.
Click Next (Done) to navigate to the summarize page:
The Working-Set creation runs in the background. You will receive a notification email and the following message will appear in the browser:
 | If an error is encountered during the creation, you are notified by via email and a message in the browser. |
Validation
Before creating or extending the Working-Set Codebeamer validates that:
• The name of the Working-Set is unique.
• The total number of items in the included trackers is less than a specified number (the default is 10000).
Background Job
Both the Working-Set creation and extensions run in the background. The Working-Set is unavailable until the job is done. You are notified when the creation is complete.
By default, the Working-Set jobs run sequentially one after another.
In case of a server restart, the background job can recover from an inconsistent state. Before running the job. Codebeamer checks if the job had been running before to clean up the inconsistent state, and then restarts the process from the beginning.
Baseline Creation
During the Working-Set creation or extension two type of baselines are used:
• A temporary baseline, that is created when the user requests the job. It ensures that even if a long job is in the queue, the Working-Set is created from the requested 'state'.
• A permanent baseline that is created right after the Working-Set creation is done. The baseline name is the same as the name of the Working-Set. When you rename the Working-Set, it also triggers the baseline renaming.
Migrating Existing Branches / Orphan branches
Branches can be built by creating a Working-Set, which must be associated with another Working-Set to be accessible for the users. To continue working with the existing branches, assign them to an existing or a new Working-Set.
If there is an orphan branch of a Tracker, for example, Tasks, that does not belong to any Working-Sets, it can be selected if the parent Tracker is selected.
In this case, the already existing branch is used and behaves as an included Tracker. Therefore, no new branches will be created for that.
If there is more than one orphan branch belonging to a Tracker, only one of them can be selected to be included.
| | After the branches are migrated into Working-Sets, you can use only new baselines. To use old baselines created for the branch, running the relevant one of the following scripts is necessary: In case assistance is needed for the execution of the scripts above, contact PTC Technical Support. |
Reference Rewriting
This section describes how references to items and the corresponding configurations are rewritten during the creation of working-sets.
| | Despite the fact that you can configure references outside of working-sets, currently you can select reference items only within the current working-set. |
Included Trackers
1. The included tracker (Task) references an included tracker (User Story):
◦ Both trackers are branched, and a reference is added between them.
2. The included tracker (Task) references a shared tracker (User Story):
◦ The included tracker is branched, and references the shared tracker(User Story).
3. The included tracker (Task) references an excluded tracker (User Story):
◦ The included tracker is branched, however, the reference is not added.
Shared Trackers
1. The shared tracker (Task) references an included tracker (User Story):
◦ The included tracker is branched, and a new reference is added to it.
2. The Shared tracker (Task) references a shared tracker (User Story):
◦ Nothing changes.
3. The shared tracker (Task) references an excluded tracker (User Story):
◦ Nothing changes.
Excluded Trackers
1. The excluded tracker (Task) references an included tracker (User Story).
◦ The included tracker is branched, but the reference is not added.
2. The excluded tracker (Task) references a shared tracker (User Story).
◦ Nothing changes.
3. The excluded tracker (Task) references an excluded tracker (User Story).
◦ Nothing changes.