Options Tab for Project Types

The Options tab of the New/Copy/Edit Object Type dialog box for projects enables you to set additional options for the rules and behavior of the project type.

NOTE
These are the default values for a new project of this type. You can override some of these when you create a new project.

For the project type STREAM, some of these options are grayed out, and cannot be changed.

Field | Description
Project is trunk | Treat the project as a trunk. When this option is unchecked, the project is treated as a branch. For a stream (project type STREAM) this is unchecked by default, and cannot be changed
Automatic revision generation | Calculate revision strings automatically. When this option is unchecked, the user supplies a revision ID. For a stream (project type STREAM) this is checked by default, and cannot be changed
Parallel check out | Allow an item revision to be checked out by multiple users at a time. For a stream (project type STREAM) this is unchecked by default, 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. 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 type or request type.
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. 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.
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.

NOTE If neither Always disable CM rules nor Always enable CM rules is set, the default behavior is for items in a project to follow the CM rules as defined for their item types. For details, see CM Rules Section for Items.

Related Topics

Adding a New Object Type

About Project Type Options