Personal streams are private development branches that are only visible to the originator. Personal streams enable you to:
Isolate work from an existing public stream.
Work in a dedicated personal stream until your changes are ready to be merged back into a public stream.
Create a new stream based on a work area. You are working on changes in a work area but the changes cannot be delivered to the associated stream. For example, the stream may be locked or the feature has been dropped from the release. To shelve your work you can create a new personal stream based on the work area, see Shelving Streams.
Personal streams are different to regular streams:
By default any user can create a personal stream.
Only the stream originator can view, and work with, a personal stream. However a user with the appropriate permissions (by default the ADMIN group) can delete a personal stream.
By default CM Rules are disabled for personal streams therefore users do not have to specify requests when delivering changes to personal streams. This behavior can be changed by an administrator.
Like regular streams, personal streams are versioned so if you deliver multiple times you can restore to any previous state. Personal streams have a unique icon to differentiate them from regular streams and projects:
To create a personal stream, create a new stream and select the appropriate option. For details see Creating a New Stream. After work on a personal stream is complete you can merge it into a regular stream, see Merging Changes across Streams.
Deleting a personal stream is the same as for regular steams, see Deleting a Stream. To avoid taking up space in your database, and to optimize performance, the recommended best practice is to delete all personal streams that are no longer required.