Configuring a template in Gaia for Jira

Configuring a template

For creating projects in Jira, you have to configure Gaia templates in the Jira Administration → Manage apps → Gaia Configuration page.

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 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	This option lets you specify assignee or use the assignee from the XML file.
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. Please note that if you are importing issues (configured in the Issues Template setting) that are associated with versions/components, and that you have not defined those versions/ components in your Gaia template, the missing versions/components will be automatically created and associated with the issues being imported.
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. Jira Core In Jira Core, the Default Issue Type Scheme is empty by default. To avoid badly created projects, it is recommended that you create your own Issue Type Schemes for all your projects, and associate them with Gaia templates. 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. More info on Workflow Schemes can be found here.
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. More info on Field Configuration Schemes can be found here.
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. Mark “Enable sending notification while creating new project“ checkbox if you want users to get notifications while creating a new project according to the configuration of the selected Notification scheme. More info on Notification Schemes can be found here: here.
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.

Scheme Duplication

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	Do not import a Jira issues file - select this option if you don't want to import issues when creating projects from the template. This is the default option when creating a template. Import your own Jira issues file - specify an XML Jira issues file in your template. This file is a set of predefined issues that will be instantiated with a new project. The Jira issues file will be stored on the server. If an issue type in the Jira Issue file is not in the issue type scheme you've selected, Gaia will choose the default issue type from the default issue type scheme. If no default issue type is set for Jira 7.x/8.x: the missing issues will be created and added to the Default Issue Type Scheme. Please know that third party and apps custom fields are not supported. Click here to expand the supported custom fields Supported Jira native custom fields: Checkboxes; Date Picker; Date Time picker; Group Picker (multiple groups); Group Picker (single group); Labels; Number Field; Radio Buttons; Select List (cascading) Select List (multiple choices); Select List (single choice); Text Field (multi-line); Text Field (single line); URL Field; User Picker (multiple users); User Picker (single user); Version Picker (multiple versions); Version Picker (single version). Supported Apps custom fields: Okapya Checklist; Tempo Team; Portfofio Team.
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	Do not import a Confluence space template - сhoose this option if you don't want to associate a Confluence space to your template. Therefore, no Confluence space will be created when creating new projects from this Gaia template. You should check this option if you don't have Confluence installed. Import your own Confluence space template - сhoose this option to import your own Confluence space template when you create new Gaia projects. See how to create your own Confluence template file for the complete procedure. Please note that using a template that needs to create a Confluence space requires that you have an application link setup between your Jira and your Confluence instance.

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 :

A checklist dashboard to display the relations between Tasks and their associated Sub-tasks. This is based on the default template "Checklist for Product Owner".
A software development dashboard to keep project leads up to date with their project progress in a single view (this dashboard is partially based on this post https://www.atlassian.com/blog/jira-software/5-steps-to-build-a-killer-dashboard).
Agile Dashboard to show content that’s relevant for agile teams. The Jira Dashboard for Agile projects is based on this post https://www.atlassian.com/blog/jira-software/7-steps-to-a-beautiful-and-useful-agile-dashboard.

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.

What's next

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.