- Configuration
- First steps
- Project setup
- Sample templates
- Migration to Cloud
- Supported fields
- Permissions
- Jira Service Management
- Template management
- Create a template
- Template configuration
- Variables
- Template Navigator
- Delete a template
- Use as a template
- Set of Fields - advanced features
- Using template
- Autocomplete
- Default Template
- Apply template
- Use Template in Jira Automation
- Automatic create and close
- JQL Searchers
- Direct links
- Create Structure post function
- About Create Structure
- Create Structure configuration
- App integrations
- REST API
- ScriptRunner and Groovy scripts
Default Availability
Discover different ways to manage the availability of your templates
New templates are available and active by default. The Default availability settings allow you to define following configurations for all the templates in your Template Repository:
- Make all new templates unavailable by default
- Make all new templates available by default in all the contexts
- Define a default context for new templates
- Require that a context must always be defined
This feature is particularly useful for managing the availability of different issue types. While Template and Sub-Template issue types can be managed with the Disable Template post function in their dedicated workflow scheme, all other issue types can be defined here.
All the following settings work only for newly created templates. The configuration won’t affect templates that already exist in your Template Repository project.
Configuration
Steps
To configure the default availability:
- Open the Template Repository project settings.
- Select Default availability from the project navigation.
- Click the arrow to expand all options.
- Decide if the templates should be available by default in all contexts.
- Configure the default context for new templates.
- Determine if defining context for existing and new templates should be required.
Result
Configured settings apply to all the templates in your repository.
Scroll down to see possible configurations.
Make all new templates unavailable by default
Steps
To make templates unavailable by default:
- Open the Template Repository project settings.
- Select Default availability from the project navigation.
- Turn off the toggle next to Create Issue Screen.
- Turn off the toggle next to Request form.
Result
All new templates will be unavailable by default.
Make all new templates available by default in all the contexts
Steps
To make new templates available by default:
- Go to Template Repository project settings > Default availability.
- Make sure that none of the contexts is set as required (or a default value is configured for each required field).
- Turn on the main toggle on the left side.
Result
All new templates will be available by the default.
- Existing templates that already have a specified context will retain their settings.
- The same applies to the Request form configuration.
Define a default context for new templates
Steps
To define a default context for new templates:
- Go to Template Repository project settings > Default availability.
- Under Default value for new templates, provide a value for the chosen context.
Result
Availability of all new templates will be limited to the specified context.
Existing templates will retain their settings.
Require that a context must always be defined
Steps
To require that a context must always be specified for every template:
-
Go to Template Repository project settings > Default availability.
-
Turn on the toggle next to the context that should be required.
NoteThe global availability (the main toggle to the left) will be automatically turned off.
-
Click Templates list in the info box to open a list of templates that have to be configured.
InfoYou will be redirected to the Template navigator where you’ll see a filtered out list of all the templates that require additional configuration.
-
Select the template that needs to be configured and open its Availability tab.
-
In the info box, click Configure now.
WarningAfter clicking Configure now the template will become unavailable for the time of the configuration. You’ll be able to make it available again after filling in all required fields.
-
Click the arrow to expand all options.
-
Define a value for the required context.
-
Turn on the toggle to make the template selectable on the Create issue screen in the specified context.
Result
The chosen context is set as required. The template is configured to be selectable in the specified context.
The same applies to the Request form configuration.
If you can’t find the answer you need in our documentation, raise a support request.