Share this page

# Create a project

Create a project to start a new phase of development. You can create a project from scratch and add items to it later.

For details on how to modify a project's default settings, see Open projects and set defaults.

PRIVILEGES: Create Project.

To create a project:

1. In the web client, open the Projects view.

2. On the toolbar, click New, and select Project.

3. In the New Project dialog box, specify the following project details and click Next:

   Field | Description
   --- | ---
   Product | Select the product in which to create the new project.
   Project name | Enter a name for the project.
   Type | Select a project type from the list.
   Description | Enter a description for the new project.

4. Specify the source on which to base the project, and click Next:

   Field | Description
   --- | ---
   Nothing (empty project) | Select this option to create an empty project.
   Based on project | Select to populate the project with the item revisions from another project. Then select the project from the list.
   Based on stream | Select to populate the project with the item revisions from a stream. Then select the stream from the list.
   Based on baseline | Select to populate the project with the item revisions from a baseline. Then select the baseline from the list.
   Copy build configuration | Select this option to copy the build configuration from the parent project to the new project.

   Note: If lists of streams or baselines are large, these fields are displayed as text boxes with browse buttons, and you can browse to select a stream or baseline.

5. Set version management options:

   Field | Description
   --- | ---
   Branch | Select this option to increment version numbers by adding a period before the new number. For example, if an item's revision number is 2, the item's first new revision in this project is 2.1, and the next one is 2.2. But for new items, the first revision number is 1, and the next one is 2.
   Do not branch | Select this option to increment version numbers by adding 1 to the previous revision number. For example, if an item's revision number is 2, the item's first new revision in this project is 3, and the next one is 4. If an item's revision number is 2.1, the first new revision is 2.2. Note: We recommend that you use this option and assign a single branch.
   Allow user to override default revision number | Select this option to allow users to change the automatically generated revision number when they create new item revisions.

6. Define the options for Change Management rules, and click Next:

   Field | Description
   --- | ---
   Use item type settings | Select this option to make items follow the CM rules, as defined for their item type in the Administration Console.
   Always enabled | Select this option to make items behave as if the CM rules defined for their item types are enabled, regardless of whether they are enabled in the Administration Console.
   Always disabled | Select this option to make items behave as if the CM rules defined for their item types are disabled.
   Request required to refactor | Select this option to require users to specify a request ID when they make refactoring changes, such as moving or renaming items or project folders. Note: You cannot relate refactoring changes as In Response To a request if the request is above the initial stage in the Global Stage Lifecycle (GSL).

7. To specify how to handle item deployment, set the Use local stages option, and click Next.

   The Use local stages option determines whether the stage of item revisions in this project is affected by changes in other projects/streams. This option enables the following behavior:

   Use local stages is selected | This preserves the stages of item revisions from changes caused by actioning. The stage of an item revision in this project remains unchanged when the same item revision in another project/stream is promoted/demoted to another stage. As a result, the same item revision can be at a different stage in different projects/streams.
   Use local stages is cleared | Promoting/demoting an item revision in another project/stream to another stage changes the stage of the same item revision in this project.

   If an item's lifecycle states are mapped to stages in the Global Stage Lifecycle (GSL), then the stage of an item revision can also be changed when the item revision is actioned to those states.

   Note: After you select this option, you cannot clear it. If your project is using Deployment Automation, this option is always selected.

8. Select valid branches and the default branch for new item revisions:

   Field | Description
   --- | ---
   Valid branches | Select one or more valid branches to which future revisions in this project may be assigned.
   Default branch | Select the default branch to use for new item revisions in this project.

9. (Optional) To set user-defined attributes, click Next. On the Attributes page, enter any required attributes.

10. (Optional) To review the summary of options, click Next.

11. Click Finish.

Back to top

See also:

- About projects

https://admhelp.microfocus.com Dimensions CM 8942
Tips to improve your search results... Dimensions CM Help Center CM Help 14.7 All View Local Help Center View Online Help Center Version: