Branch Project: Project Information

The Project Information page in the Branch Project wizard identifies the essential information needed to create the branched project. Certain fields are pre-populated with values from the current project but can be edited as needed for the new project. After you complete the fields and click Next, the branched project is created if the information you provided is valid.

For a description of the procedures related to the Project Information page, see the following:

• Branching a Project
• Step 1: Creating the Branched Project

The following describes the properties and actions available on the Project Information page:

Branch Project: Project Information Page

Field

Description

Name

Enter a name for the branched project. The name must be unique in your Code Insight system.

Description

If necessary, edit the description for the branched project. This field is initially populated with the description of the source project.

Policy Profile

If necessary, select a different policy profile for the branched project to automate its inventory review process. This field is initially populated with the policy profile used by the source project.

A given policy profile uses a combination of policies to automatically mark published inventory items as approved or rejected without the need of a manual review. (Inventory items that are neither approved or rejected by policy are marked as Not Reviewed and will require a manual review.) For more information about policy profiles, see Policy Details Window and Managing Policy Profiles.

Scan Server

If necessary, select a different Scan Server that will scan the codebase for the branched project.

This field is initially populated with the Scan Server used by the source project.

Scan Profile

If necessary, select a different scan profile that defines the settings applied whenever the branched project is scanned.

This field is initially populated with the scan profile used by the source project.

Project Visibility

If necessary, change the visibility attribute—Public or Private—of the branched project.

• Public—A project that provides read-only access to any user in the system. To what degree a user can interact with the project depends on whether the user has a project role and what the role is—Project Administrator, Analyst, or Reviewer.
• Private—A project that is hidden from all users except the Project Contact and those users assigned as Project Administrators, Analysts, Reviewers, or Observers of the project. Additionally, project and vulnerability ID searches will not return private projects unless the user performing the search has the permissions to see a given private project.

This field is initially populated with the attribute of the source project.

Project Risk

If necessary, change the vulnerability risk value (Low, Medium, or High) of the branched project. This field is initially populated with the risk value of the source project.

Project Status

If necessary, change the status of the branched project. (The meaning of these statuses might be adjusted for your site.)

• Not Started—Indicates that the project scan results are not yet available for manual analysis.
• Analysis in Progress—Indicates that the project scan results are available for manual analysis, or a manual analysis is underway.
• Analysis Completed—Indicates that manual analysis is finished; and the published inventory is ready for legal, security, or software-engineering review.
• Project Complete—Indicates that the project analysis and review processes are complete, and notices content for all OSS and third-party software is finalized.

This field is initially populated with the status of the source project.

Source Code Options

Select one or both options (or neither option) defining the method for obtaining source code for branched project:

• Upload Codebase—The source codebase is uploaded from an archive accessible from current instance. By default, this option is always selected. (You can upload multiple codebases.)
• Sync from Source Control—The source code base is obtained through a synchronization process with one or more instances of your site’s Source Control Management (SCM) system. For more information about the synchronization process with SCMs, see Configuring Source Code Management. This option is selected by default only if SCM instances were configured in the source project.

Alternatively, to copy only inventory and inventory-review information from the source project to the branched project, do not select either of these options. No file information will be associated with the inventory copied to the branched project.

Copy Project Users

Select the option that determines whether project roles of the source project are copied to the branched project:

• Yes—All current project-role assignments—including Project Administrators, Analysts, Reviewers, Observers, and the Legal, Developer and Security contacts—are copied from the source project to the branched project once the branching process completes. (This is the default for the branching process.)

The user who performs the branching process is assigned the Project Contact role.

• No—The Project Administrator user who is creating the branched project is assigned to each of the project roles in the branched project. Additionally, those users assigned to roles by the System Administrator as global defaults for all new projects are added to the branched project (see “Setting Project Defaults” in the Code Insight Installation & Configuration Guide).

Retain Child Project Links

Select the option that determines whether the entire child hierarchy of the source project is copied to the branched project. This hierarchy includes the child projects directly associated with the source project, any child projects of those projects, and so on. (See Identifying Child Projects for a Project for more information about project hierarchy.) When this hierarchy is copied, links to the child projects are also copied.

This option does not copy the parent hierarchy that might be associated with the source project.

• Yes—The entire child hierarchy of the source project is copied to the branched project, along with links to the projects in the hierarchy.
• No—The child hierarchy of the source project is not copied to the branched project.

Next

Click this button to create the project and move to the next wizard page:

• If selected Upload Codebase in the Source Code Options section, the Branch Project: Upload Codebase page opens.
• If you selected only Sync from Source Control in the Source Code Options section, the Branch Project: Version Control Settings page opens.
• If you selected neither option, the Branch Project: Project Copy Settings page opens.

However, if errors are found on this page, you must correct them before the project can be created and you can move to the next page.

Cancel

Click this button to cancel the project-branching setup.