Creating change sets in the RM application
A change set is a collection of related modifications to artifacts. You can create change sets to create convenient groupings of changes; for example, a group of changes that resolves a problem. Other team members can load your change set to review your changes before you deliver them.
Before you begin
- Ensure that you are familiar with project areas, components (if supported), baselines, streams, and change sets (if supported).
- Ensure that you are familiar with global configurations and personal streams (if your organization uses them).
- Ensure that you are logged in to a project.
- Ensure that the current configuration is a stream.
- You must have permission to create change sets.
- Understand how your organization uses streams, baselines, and change sets based on how many teams need to work in parallel on different versions of the same artifacts. To learn more, see Patterns for stream usage on Jazz.net.
About this task
When you change artifacts in the context of a change set, all the changes that you make are grouped into one logical unit. This grouping facilitates the review process and makes it easy to share changes with other teams or team members that use different streams.If you do not create change sets, each time that you save your changes to an artifact or link in a stream, the application automatically creates and delivers a change set, and your changes are available immediately to other team members who share the stream. Even though working this way is simple, it can be harder to identify and deliver specific change sets to other streams. Ask your team lead or configuration lead for guidance about whether to manually create change sets to manage your changes.
To increase traceability in the development lifecycle and prevent the delivery of unauthorized changes, you can link the change set to a work item.