Defining a project

PDF

To configure a project in JIRA:

1. Log in as a user with the 'JIRA Administrators' global permission.

2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard:

   

3. Select an existing project, or click Add Project to add a project.

Here is what a project looks like once created:

A project's configuration settings are as follows:

• Key - a 'key' unique to this project (eg. 'WEB'), which specifies the first few letters of this project's issue keys (eg. 'WEB-100').
• URL - An optional URL associated with this project, eg. pointing to project documentation.
• Project Team:
  • Project Lead - user fulfilling the role of project leader. Used as the 'Default Assignee' (see below), and potentially elsewhere in JIRA (eg. in permission schemes, notification schemes, issue security schemes and workflows).
  • Default Assignee - the user to whom issues in this project are initially assigned when created. Can be either the 'Project Lead' (above), or, if Allow unassigned issues is set to 'On' in JIRA's general configuration, 'Unassigned'. Note: in JIRA Enterprise there are also default component assignees.
  • Project Roles - members are users/groups who fulfil particular functions for this project. Project roles are used in permission schemes, notification schemes, issue security schemes and workflows.
• Issue Type Scheme (Enterprise and Professional only) - the project's issue type scheme determines which issue types apply to this project.
• Notification Scheme - the project's notification scheme determines who receives email notifications of changes to issues in this project.
• Permission Scheme - the project's permission scheme determines who has permission to view or change issues in this project.
• Issue Security Scheme (Enterprise only) - the project's issue security scheme determines what visibility levels issues in this project can have (see issue-level security).
• Field Configuration Scheme (Enterprise only) - the project's field configuration scheme determines which field configuration applies to issue types in this project. (A field configuration determines fields' overall visibility, requiredness, formatting (wiki/rich-text or plain) and existence on various screens).
• Screen Scheme (Professional only) - the project's screen scheme determines which screens are displayed for different issue operations (view, edit, create); or:
• Issue Type Screen Scheme (Enterprise only)- the project's issue type screen scheme determines which screens are displayed for different issue operations (view, edit, create), for different issue types.
• Workflow Scheme (Enterprise only) - the project's workflow scheme determines which workflows (issue state transitions) apply to issue types in this project.
• CVS Modules - configures CVS integration for this project.
• Mail Configuration (Enterprise only)- specifies the 'From' address for emails sent from this project. Only available if an SMTP email server has been configured in JIRA.
• Project Category (Enterprise only) - a logical category to group this project into. Useful for managing multiple related projects. New categories can be created via the 'Project Categories' link in the 'Administration' menu.

As well as:

• Components - logical groups that this project's issues can belong to. See the component management page for details.
• Versions - versions defined in the project. See the version management page for details.

A note about Project Administrators