Topic Streams

Topic streams are temporary streams that you use for a set of defined changes, for example, to fix a defect or develop a small feature. Topic streams enable you to isolate your changes from a mainline.

Key Facts

• By default any user can create a topic stream.

• Topic streams are versioned the same as regular streams.

• Have their own icon to differentiate them from regular streams .

• Are usually only visible to the user who created them but other team members can be given access by delegating the topic stream or changing its ownership.

• After you delegate a stream that you created you can continue contributing to it. Access is controlled by the privilege Manage Topic Streams. All users in the ADMIN group have this privilege granted by default.

• CM Rules are disabled by default so you do not have to specify requests when delivering changes.

Differences between Topic and Regular Streams

• Topic streams have less features and are typically used for short-term work.

• You cannot create a topic stream from another topic stream.

• A topic stream and its parent stream must belong to the same CM product.

• A topic stream cannot be deployed, baselined, or added to a CM release.

• A topic stream can only be related to a single, active pull request. After the related pull request has moved to its final state, or been abandoned, you can relate another pull request.