About Project Type Options

Project is trunk

When set, the numbering of item revisions is determined by incrementing the last numeral. For example, if an item is at revision 5, subsequent revisions would be 6, 7, and so on.

When the option is not set, item revisions are incremented by appending a period before the new number. For example, if a branch is created from revision 5, would be 5.1, 5.2, and so on.

For streams, by default this option is not set, and cannot be changed.

Automatic revision generation

When set, new revisions are automatically generated when an item is edited or updated.

When the option is not set, new revisions are not automatically generated. The user is asked to supply a revision ID.

For streams, by default this option is set, and cannot be changed.

Parallel check out

When set, an item revision in this project can be checked out by multiple users at a time.

Note that:

• This will be overridden by the Allow Parallel Checkout setting for an individual item type. (See About Item Type Options.)

• This setting will only apply to newly created projects of this type. To change this option for existing projects you will need to use the UWA command. (See the Command-Line Reference for details.)

For streams, by default this option is not set, and cannot be changed.

Use local stages

This deployment related option determines whether the stage of item revisions is "local" to this project/stream or can be affected by changes in other projects/streams. (Note that this means that the same item revision could be at a different stage in different projects/streams.)

• If you select this option, the stage of an item revision in this project/stream is not affected when the same item revision is promoted/demoted to another stage as a result of activities in any other project/stream.

• If you do not select this option, when an item revision in any project/stream is promoted/demoted to another stage, then the stage of the same item revision in this project/stream will also be updated.

Note: The stage of an item revision can also be changed when it is actioned if its lifecycle states have been mapped to stages in the GSL.

Always disable CM Rules

When set, a project of this type will have the option for CM rules for items in that project set to Always disabled by default when it is created (but you can override this). When this option is set for a specific project, item operations in that project will act as if CM Rules were not enabled for any item types or request types.

Always enable CM Rules

When set, a project of this type will have the option for CM rules for items in that project set to Always enabled by default when it is created (but you can override this). When this option is set for a specific project, item operations in that project will act as if CM Rules were enabled for all item types and request types. For details of these CM Rules, see CM Rules Section for Items.

Require change control when refactoring

When set, a project of this type will have the option Request required to refactor set by default when it is created. When this option is set, the user will be required to provide a request ID when making any refactoring changes to the project, such as moving or renaming items or project folders.