For creating projects in Jira, you have to configure Gaia templates.
Gaia Configuration page allows you to add, edit, copy, import, export, disable and remove Gaia templates.
| Info |
|---|
You have to be a Jira Admin to manage Gaia for Jira templates. |
| Table of Contents | ||||
|---|---|---|---|---|
|
Adding a template
To add a new template, perform the following steps:
1. Go to the Jira Administration → Manage apps → Gaia Configuration page.
2. By default, you have 3 available pre-defined Gaia templates. You can copy and edit them as a basis for a new template.
3. To add a new template, click on the Add button on the upper right side of the page. The following dialog opens :
...
Most of the configuration options refer directly to Jira project configuration items. Make sure you enter a template name and a template description, as they are required to save a template. All other options can be left to their default values.
To get a description of each configuration option, go to the Configuring template section of this guide.
Configuring a template
This section provides a description of all options that are available for the Gaia template configuration.
Template details
Template name | The template name is the name that users will see when they create a project from a Gaia Template. Template names must be unique and alpha numeric. |
Template description | The template description is shown in the list of templates in the administrative section of Gaia. Use it to describe the purpose of the template. |
Project Details
Project description | In this field, add the default project description to add to the Jira project. This description is visible in the summary when you select the project. | ||
Project Type | Select if you wish this project to be categorized as a Business (Jira Core), Software (Jira Software) project, or Service Desk project. | ||
| Project default assignee | |||
Project category | Projects can have categories to help with sorting and other Jira features. The default category for each created project can be set. More info on Project categories can be found here. | ||
| Versions | These options let you add a list of versions/ components that will be added at the creation of a project.
| ||
| Components |
Schemas
Issue Type Scheme | Select the issue type scheme to apply when new projects are created. An issue type scheme determines which issue types will be available for a set of projects.
More info on Issue Type Schemes can be found here. | |||||
Workflow Scheme | Select the workflow scheme to apply when new projects are created. A workflow scheme determines which workflow is used for each issue type in the project. | |||||
Issue Type Screen Scheme | Select the issue type screen to apply when new projects are created. An Issue Type Screen Scheme allows you to choose which Screen Scheme is used for each issue type in the project. More info on Issue Type Screen Schemes can be found here. | |||||
Field Configuration Scheme | Select the field configuration scheme to apply when new projects are created. Field Configuration Schemes determine which Field Configurations apply to issue types in the project. | |||||
Priority Scheme | This option will only appear if you have Jira Server 7.6 or above. Select the priority scheme to apply when new projects are created. Priority Schemes allow you to create a set of priorities for issues and apply this set of priorities to any project. More info on Priority Schemes can be found here: here. | |||||
Issue Security Scheme | Select the security scheme to apply when new projects are created. Issue Security Schemes allow you to control who can and cannot view issues. They consist of a number of security levels that can have users/groups assigned to them. More info on Issue Security Schemes can be found here. | |||||
Notification Scheme | Select the notification scheme to apply when new projects are created. Notification Schemes allow you to control who to notify when a given event fires. | |||||
Permissions Scheme | Select the permission scheme to apply when new projects are created. Permission Schemes allow you to create a set of permissions for users and apply this set of permissions to any project. More info on Permission Schemes can be found here: here. |
| Info | ||
|---|---|---|
| ||
Under each scheme selection dropbox, there is an "Enable scheme duplication" option. When checked, this enables that scheme to be duplicated at the project creation. However, the user creating the project using that template must choose to create a copy of the schemes at that moment. Only the schemes with the "Enable scheme duplication" option checked will be duplicated and applied to the newly created project. In the case of the Workflow scheme and the Issue type screen scheme, you also have to option to include their child objects in the duplication. |
Files
Issues template |
| |||||||
Issues comments | If checked, the comments associated with the imported issues will be included in the template. Otherwise, they will be ignored. | |||||||
Tempo Teams | If checked, the Tempo Team's values from the imported issues will be included. This setting is only present if the Tempo plugin is installed and is enabled. If enabled, this setting will make the option to create a tempo link appear when the template is selected while configuring a new project to create. | |||||||
| Space template |
|
Boards
| Filters | This option, when enabled, creates a project-specific filter for each issue type found in your project and a filter for all issues in the project. These filters are shared with all users. This can be useful to quickly create dashboards with custom filters to help your team use the system. |
| Dashboard | This option automates the creation of a pre-defined dashboard when creating a project. There are three pre-defined dashboards in Gaia for Jira :
To enable the automated adding Dashboards and Filters when creating a project, confirm if the Sharing with anyone on the web functionality is on. |
| JIRA Agile board | This option automates the creation of Jira Boards when creating a project. You can find more information on Jira Agile here. |
Project Roles
| Project Roles | This setting lets you select the roles you want to associate with the project that will be created. You can include multiple choices. Please note that you have to provide the username of the user and not its full name. When the project is created using a template that contains Project Roles, only existing and active users and groups will be taken into consideration. All invalid users and groups will be omitted at the time of the project creation. |
Once you've configured your template , click and clicked on Save button. You should see your , you will see the new template in the template list:
...
| Tip | ||
|---|---|---|
| ||
If you want to create your own Jira issues file or your own Confluence Space files, refer to this guide for Jira and this guide for Confluence. |
What's next
You can now add as many templates as needed.
The next step is up to you. You can edit your template, copy your template or even delete it if you no longer need it.