This chapter describes the Advanced Dynamic Variables feature, available on the Advanced plan.
This feature is available to users of the Advanced edition of the Issue Templates app.
Advanced Dynamic Variables let you create and manage variables in a shared library - at the space or global scope - so you can reuse them across multiple templates without re-entering definitions each time. Variables support default values and can be marked as required per template.
Dynamic variables can be used in two ways - Basic and Advanced - and within Advanced, variables exist at three levels of scope.
Backward compatibility
Templates that already contain manually entered variables (Basic format, for example [Variable name]) continue to work without any changes. The app recognizes both formats. You don’t need to convert existing templates before using the Variable Library, but it’s recommended to fully use the feature.
If you already have variables created in the Basic (legacy) format, they will not appear in the Variable Library until you convert them. See Converting existing variables to Advanced format for details.
| Field name | Description |
|---|---|
| Command/Name | The internal identifier used in template placeholders (for example, [Employee name]). This is what the app uses to match the variable in template content. |
| Field type | The type of a field related to the options of the variable. Supported types: Labels; Date; Date & Time; Issue; Multi Select; Paragraph; Single Select; Sprint; Team; Text; User; Users |
| Label | The user-facing name shown in the creation form when someone fills in the variable. |
| Description | Additional variable information - optional. |
| Required | Select if you wish to force users to select something. |
| Default value | Value populated by default, might suggest users what to place. |
| Availability | Global or Space (depends if you wish to have variables available for all spaces or just some). |
The process is the same as for global variables. Navigate to Space settings → Apps → Issue Templates for Jira → Dynamic variables instead of the global configuration. The field table is identical - the only difference is that Availability defaults to Local, so the variable is scoped to the current space only.
After you define variables in the library, you can add them to any template. Variables are selected through the template configuration wizard.
Open the template you want to edit and scroll to variables under Issue Templates on the sidebar.
Click the Copy icon and paste into the work item description.
If you haven’t created any variables yet, or wish to add a new one, click Create new variable+.
Click More to expand variable information, it shows the label, options and availability.
Click Save.
Your template now provides dynamic variables. If someone uses the template, they will be prompted to insert necessary information.
If you have existing Basic dynamic variables, you can convert them to the Advanced format to take advantage of the shared library, default values, and cross-template reuse. The variable placeholders in the template content (for example, [Employee name]*) are preserved exactly as they are - the content of your templates doesn’t change during conversion.
There are two separate conversion options depending on the target scope:
This option is always available, even after migration. It scans template content across all active repositories, extracts unique placeholders with their types and options, and saves them to the global library. Each candidate variable gets one of two statuses:
The converted variables appear in the Variable Library as space variables. They’re automatically linked to the template and can now be reused in other templates, have default values set, and be managed centrally.
From the space library, you can bulk-promote local variables to space level, making them available to all templates within the space.
The promoted variables move from template-level (local) to the space library and become available to all templates in the space.
Before a variable is removed from the library, the app displays a warning listing every template that currently uses the variable. This lets you assess the impact before confirming the deletion.
After deletion, any placeholder text referencing that variable in the template content remains unchanged. The variable is simply no longer listed in the template’s variable configuration and won’t appear in the creation form.
You can promote a local variable to global scope so it becomes available across all repositories. If a global variable with the same name already exists, the promotion is blocked to prevent naming conflicts.
Advanced Dynamic Variables are supported while creating work items via the issue.templates.automation property — the same as Basic variables. See the Automation chapter for details.