Creating project areas

You can create a project area in a repository for managing the project deliverables, team structure, process, and schedule.

Before you begin

You must be a member of either the JazzProjectAdmins group or the JazzAdmins group.

About this task

If you are creating project areas in multiple applications, such as change and configuration management, quality management, and requirements management, and you want to associate these project areas with each other, consider creating a lifecycle project. A lifecycle project groups multiple project areas and provides a central location from which you can manage members of the project areas. See Administering lifecycle projects for details.

To create a requirements management project area, following the instructions in Creating requirements projects.

When you create a project area, you must specify the process that the project area will use. To specify the process, you typically select a process template. Alternatively, you can have the new project area consume the process from another project area. The other project area must share its process before you can have the new project area consume it. Project area process sharing allows an organization to centralize process in one project area.

Procedure

  1. Navigate to the Project Areas tab of the administrative web interface. See Logging in for project administrators and team leads (web).
  2. Click Create Project Area.
  3. In the Project Name field, enter a project area name.
  4. Enter a brief summary and description of the project area.
  5. Specify the process that the project area will use, under Process:
    • To select a process template, ensure that Use process template to initialize this project area is selected.
      • For Quality Management, the Quality Management Default Process is intended for use with new project areas. The Quality Management Legacy Process is available to support older projects that contain local Defect and local Task-Quality work items. Project areas that have been migrated from earlier versions of the product use the Quality Management Legacy Process.
      • If your team has custom process templates in the repository, select a process template from the Available Processes list.
      • If your team does not have custom process definitions in the repository, click Deploy predefined process templates. From the list, select one of the predefined process templates. Deploying predefined process templates applies only to Change and Configuration Management project areas. You need to deploy the predefined templates only once.
        Attention: If you upgrade from a previous release, deploying templates overwrites the previous versions of those templates. If you have customized the templates and want to preserve those customizations, open the templates in the Process Template editor; change their IDs and names; and save them before you deploy the new predefined templates.
    • To have the project area consume the process of another project area that shares its process, select Use the process configuration from another project area for this project area. Click Change next to Project Area, then select the sharing project area.
      Note: When you choose this option, no template is used to create the project area. If you want the project area to consume the process of another project area, but that other project area is not currently ready to share its process, you can select Use process template to initialize this project area and select Unconfigured Process from the list of available processes. Then, when the other project area shares its process, you can modify this project area to consume the process of the other project area. The Unconfigured Process template does not configure any process on its own. The Unconfigured Process template is available for Change and Configuration Management and Quality Management project areas.
      Note: When you choose this option, no initialization actions are performed for the new project area. If you want to have initialization actions, such as creating work items, performed when the project area is created, but you also want that project area to consume the process of another project area, you can create a process template based on the Unconfigured Process template; modify the new template to include initialization actions; import the new template into the application; create the project area based on that new template; and then modify the project area to consume the process of the other project area.
  6. Optional: To add a user as a member of the project area:
    1. Under Members or Administrators, click Add.
    2. In the Select Users dialog box, enter a name to search for a particular user, or click Show All.
    3. In the Matching users pane, select a user.
    4. Click Add.
  7. Click Save.

What to do next

After you create the project area, scroll to the Members section and assign process roles to members to ensure that they have the permissions required to work on project area artifacts. If the application is configured to support cross-application communication, you can configure links to project areas in other applications so that users can create links from artifacts in the local project area to artifacts in the project area in the target application. To enable linking, add associations to the project area.