General Settings tab

To learn how to customize general settings of a P4 Code Review project, watch this video or review the instructions following the video.

Plan for members and owners

Avoid creating a project that you cannot edit. If you have specified owners, ensure that you are specified as one of the owners. Or, if no owner is specified, ensure that you have specified yourself as a member. You might or might not see a warning dialog about this situation. In such a case, the warning dialog allows you to either click Continue to save the project without your ownership or membership, or click Cancel to continue editing the project. (The project page's Save and Cancel buttons are disabled while this warning dialog is visible.)

Steps

In the General Settings tab, you can configure the following options:

Specify a project name.
Add a short description about the project.
Select a Workflow to associate with the project. Your selection is auto saved.

To remove the existing workflow without replacing it with another workflow, select No Workflow from the Workflow dropdown list. This is the default when you create a new project.

You can associate a workflow with the project branch. If you have disabled the workflow feature, this option will not be displayed.

To associate a workflow with a project branch, select one from the Workflow dropdown list, or enter the workflow name in the search field. You will only be able to see the workflows that you own or shared workflows. When a workflow is associated with a project, the workflow is used for all of the branches in that project.

To use the parent project workflow, select Inherit from project from the Workflow dropdown list. This option is select by default when you create a new branch. If the parent project is set to No workflow, the branch will use the global workflow rules. When a project branch is associated with a workflow, the workflow of the parent project is ignored and the branch workflow is used.

To remove the existing workflow without replacing it with another workflow, select No Workflow from the Workflow dropdown list. This is the default when you create a new project.

For more information about workflows and how project workflows interact with branch workflows, see Workflow basics.
Set the Minimum up votes for a project. The project setting is used on the project branches unless Minimum up votes is set to 1 or higher on a branch. In this case the branch setting is used and the project setting is ignored.

Enter the Minimum up votes or use the up and down arrow keys to increase or decrease the number of Minimum up votes. To save your changes click the green tick icon. Click the cross icon to delete your changes.

Use Minimum up votes to set the minimum number of up votes required for reviews in this branch.

A review cannot be approved until all of the Required reviewers have voted up the review and the Minimum up votes specified has been satisfied.

When this setting is defined at the project level, minimum number of up votes is automatically applied to all branches. However, if you set Minimum up votes to 1 or higher on a specific branch, that branch will use its own setting and ignore the project-level setting.

To use the project-level value, set Minimum up votes to Inherit from project. This is set by default for new branches.

To override the project setting and use a custom value for a certain branch, set Minimum up votes to 1 or higher on that branch.

Notes on minimum up votes
- If a review includes changes across multiple projects or branches, the minimum number of up votes on each project or branch must be met before the review can be approved.
- Required reviewers are included when counting up votes.
- When the workflow rule Count votes up from is set to Members for a project or branch, only up votes from members belong to that project or branch will count toward the minimum up votes requirement. For more information on the Count votes up from rule, see Workflow rules.
  
  If workflows are disabled, all votes are counted, not just votes from project members.
If the Minimum up votes requirement is higher than the total number of reviewers on a review, it will be impossible to approve it, even if every reviewer votes to approve. Take this into consideration when setting Minimum up votes.
Specify a Job filter.

The job filter allows you to specify criteria that are used to associate jobs with projects. For example, entering Subsystem=ProjectA associates jobs whose subsystem field is set to ProjectA with the current project.

This job filter is simpler than the filters available in other P4 Server clients. The filter must be expressed as field=value pairs; bare keywords are not permitted. The asterisk for wildcard matching is permitted, but no other filter expression syntax is permitted.
Slide the Private project toggle to make this project private. Private projects and their associated reviews are only visible to project owners, moderators, and members, plus users with super privileges in P4 Server.

To learn more, see Private projects.
Delete a project as follows:
1. Click Delete Project.
  
  A confirmation dialog appears to confirm whether you want to delete this project.
2. Click Confirm to delete the project.

After you have deleted a project, P4 Code Review will attempt to clean up the deleted project. For more information, see Delete a project.