Apps documentation
Issue Templates for Jira
Cloud Server/Data Center
Issue Templates for Jira


Server/Data Center

Release notes
Articles & Videos
Last updated Sep 20, 2021

Dynamic variables

This chapter provides information about dynamic variables.

Dynamic variables are placeholders which you can define in your primary template in text fields (e.g. summary, description). Right before issue is created from a template, dynamic variables are collected from the primary template and additional form is displayed. It’s the place where you provide values.

While placeholders are collected only in primary template, they are replaced with provided values both in primary and secondary templates.

If you defined dynamic variables in epic and used the same variable in story/subtask, all placeholders will be replaced with provided value. However, variables defined only in stories, subtasks won’t be taken into account.

One definition, many usages

It is sufficient to define a variable only once in any field. It can then be referenced only by name. Order doesn’t matter.



Equipment for new employee [equipment*| laptop| monitor| headset]*


Order of equipments for new employee: [equipment]

Dynamic variables format

To configure the format of your dynamic placeholders:

  1. Go to the Project settings in the template repository project and select Issue Templates.
  2. Click Variables tab.
  3. Select Dynamic type of variable from the drop down list.
  4. Settings of variables displays:
    a. Start pattern: Type pattern which opens variable.
    b. End pattern: Type pattern which closes variable.
    c. Mandatory mark: Type mark which user should add after end pattern to make variable required.
    d. Replace empty option: When switched on, if variable is optional, and the value is not provided, replace variable placeholder with empty string (e.g.: text: “City {{ cityVariable }} is optional” becomes “City is optional“)
Add a comment
Dynamic Variables

Dynamic variables in Automation

Dynamic variables are supported while creating issues via issue.templates.automation property.