---
title: "Configuring a template in Gaia for Jira"
canonical: "https://support.appfire.com/space/GFJ/17629696/Configuring%20a%20template%20in%20Gaia%20for%20Jira"
format: markdown
---
> Macro (aura-html)

## Configuring a template

<span style="color: #333300">For creating projects in Jira, you have to configure Gaia templates in the </span>**<span style="color: #333300">Jira Administration</span>**<span style="color: #333300"> → </span>**<span style="color: #333300">Manage apps</span>**<span style="color: #333300"> → </span>**<span style="color: #333300">Gaia Configuration</span>**<span style="color: #333300"> page.</span>

<span style="color: #333300">This section provides a description of all options that are available for the Gaia template configuration.</span>

### Template details

|  |  |
| --- | --- |
| *<span style="color: #333300">Template name</span>* | <span style="color: #333300">The template name is the name that users will see when they create a project from a Gaia Template. Template names must be </span><u><span style="color: #333300">unique</span></u><span style="color: #333300"> and </span><u><span style="color: #333300">alpha numeric</span></u><span style="color: #333300">.</span> |
| *<span style="color: #333300">Template</span>**<span style="color: #333300"> descripti</span>**<span style="color: #333300">on</span>* | <span style="color: #333300">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.</span> |

### Project Details

|  |  |
| --- | --- |
| *<span style="color: #333300">Project description</span>* | <span style="color: #333300">In this field, add the default project description to the Jira project. This description is visible in the summary when you select the project.</span> |
| *<span style="color: #333300">Project Type</span>* | <span style="color: #333300">Select if you wish this project to be categorized as a Business (Jira Core), Software (Jira Software) project, or Service Desk project.</span> |
| *<span style="color: #333300">Project default assignee</span>* | <span style="color: #333300">This option lets you specify assignee or use the assignee from the XML file.</span> |
| *<span style="color: #333300">Project category</span>* | <span style="color: #333300">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 </span>[<span style="color: #333300">here</span>](https://confluence.atlassian.com/adminjiraserver/defining-a-project-938847066.html)<span style="color: #333300">.</span> |
| *<span style="color: #333300">Versions</span>* | <span style="color: #333300">These options let you add a list of versions/ components that will be added at the creation of a project.</span><br>> ℹ️ <span style="color: #333300">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.</span> |
| *<span style="color: #333300">Components</span>* |

### Schemas

|  |  |
| --- | --- |
| *<span style="color: #333300">Issue Type Scheme</span>* | <span style="color: #333300">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.</span><br>> ⚠️ **Jira Core**
> ⚠️ 
> ⚠️ <span style="color: #333300">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.</span><br><span style="color: #333300">More info on Issue Type Schemes can be found</span> [here.](https://confluence.atlassian.com/adminjiraserver/associating-issue-types-with-projects-938847092.html) |
| *<span style="color: #333300">Workflow Scheme</span>* | <span style="color: #333300">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. </span>  
<span style="color: #333300">More info on Workflow Schemes can be found </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/managing-your-workflows-938847410.html) |
| *<span style="color: #333300">Issue Type Screen Scheme</span>* | <span style="color: #333300">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.</span>  
<span style="color: #333300">More info on Issue Type Screen Schemes can be found </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/associating-screen-and-issue-operation-mappings-with-an-issue-type-938847305.html) |
| *<span style="color: #333300">Field Configuration Scheme</span>* | <span style="color: #333300">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.</span>  
<span style="color: #333300">More info on Field Configuration Schemes can be found </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/associating-field-behavior-with-issue-types-938847262.html) |
| *<span style="color: #333300">Priority Scheme</span>* | <span style="color: #333300">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: </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/associating-priorities-with-projects-939514001.html) |
| *<span style="color: #333300">Issue Security Scheme</span>* | <span style="color: #333300">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 </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html) |
| *<span style="color: #333300">Notification Scheme</span>* | <span style="color: #333300">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.</span><br><span style="color: #333300">Mark</span> *<span style="color: #333300">“Enable sending notification while creating new project“</span>*<span style="color: #333300"> checkbox if you want users to get notifications while creating a new project according to the configuration of the selected Notification scheme.</span>  
<span style="color: #333300">More info on Notification Schemes can be found here: </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html) |
| *<span style="color: #333300">Permissions Scheme</span>* | <span style="color: #333300">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: </span>[<span style="color: #333300">here.</span>](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html) |

> ℹ️ **Scheme Duplication**
> ℹ️ 
> ℹ️ <span style="color: #333300">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.</span>
> ℹ️ 
> ℹ️ <span style="color: #333300">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.</span>

### Files

|  |  |
| --- | --- |
| *<span style="color: #333300">Issues template</span>* | - **<span style="color: #333300">Do not import a Jira issues file</span>**<span style="color: #333300"> - 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.</span>
- **<span style="color: #333300">Import your own Jira issues file - </span>**<span style="color: #333300">specify an</span> [XML Jira issues file](https://appfire.atlassian.net/wiki/spaces/GFJ/pages/17629228/Creating+your+own+Jira+issues+file) <span style="color: #333300">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. </span><br>> ⚠️ <span style="color: #333300">Please know that third party and apps custom fields are not supported.</span>
> ⚠️ 
> ⚠️ > Macro (legacy-content) |
| *<span style="color: #333300">Issues comments</span>* | <span style="color: #333300">If checked, the comments associated with the imported issues will be included in the template. Otherwise, they will be ignored.</span> |
| *<span style="color: #333300">Tempo Teams</span>* | <span style="color: #333300">If checked, the Tempo Team's values from the imported issues will be included.</span><br><span style="color: #333300">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.</span> |
| *<span style="color: #333300">Space template</span>* | - **<span style="color: #333300">Do not import a Confluence space template</span>**<span style="color: #333300"> - с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.</span>
- **<span style="color: #333300">Import your own Confluence space template</span>**<span style="color: #333300"> - сhoose this option to import your own Confluence space template when you create new Gaia projects. See </span>[<span style="color: #333300">how to create your own</span>](https://appfire.atlassian.net/wiki/spaces/GFJ/pages/17629593/Creating+your+own+Confluence+space+file)<span style="color: #333300"> Confluence template file for the complete procedure. </span><br>> ℹ️ <span style="color: #333300">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. </span> |

### Boards

|  |  |
| --- | --- |
| *<span style="color: #333300">Filters</span>* | <span style="color: #333300">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.</span> |
| *<span style="color: #333300">Dashboard</span>* | <span style="color: #333300">This option automates the creation of a pre-defined dashboard when creating a project. There are three pre-defined dashboards in Gaia for Jira :</span><br>- <span style="color: #333300">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". </span>
- <span style="color: #333300">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 </span>[https://www.atlassian.com/blog/jira-software/5-steps-to-build-a-killer-dashboard](https://www.atlassian.com/blog/jira-software/5-steps-to-build-a-killer-dashboard)).
- <span style="color: #333300">Agile Dashboard to show content that’s relevant for agile teams.</span><span style="color: #333300"> The Jira Dashboard for Agile projects is based on this post </span>[https://www.atlassian.com/blog/jira-software/7-steps-to-a-beautiful-and-useful-agile-dashboard](https://www.atlassian.com/blog/jira-software/7-steps-to-a-beautiful-and-useful-agile-dashboard).<br><span style="color: #333300">To enable the automated adding Dashboards and Filters when creating a project, </span><span style="color: #333300">confirm if the</span><span style="color: #172b4d"> </span>[Sharing with anyone on the web](https://confluence.atlassian.com/adminjiraserver/control-anonymous-user-access-975034642.html)<span style="color: #172b4d"> </span><span style="color: #333300">functionality is on.</span> |
| *<span style="color: #333300">JIRA Agile board</span>* | <span style="color: #333300">This option automates the creation of Jira Boards when creating a project. </span><span style="color: #333300">You can find more information on Jira Agile</span><span style="color: #333333"> </span>[<span style="color: #091e42">here</span>](http://confluence.atlassian.com/display/AGILE/)<span style="color: #333333">.</span> |


### Project Roles

|  |  |
| --- | --- |
| *<span style="color: #333300">Project Roles</span>* | <span style="color: #333300">This setting lets you select the roles you want to associate with the project that will be created. You can include multiple choices.</span><br><span style="color: #333300">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.</span> |


## What's next

<span style="color: #333300">If you want to create your own Jira issues file or your own Confluence Space files, refer to this </span>[<span style="color: #333300">guide for Jira</span>](https://appfire.atlassian.net/wiki/spaces/GFJ/pages/17629228/Creating+your+own+Jira+issues+file)<span style="color: #333300"> and this </span>[<span style="color: #333300">guide for Confluence</span>](https://appfire.atlassian.net/wiki/spaces/GFJ/pages/17629593/Creating+your+own+Confluence+space+file)<span style="color: #333300">.</span>