Apply template
⚙️ Automation Action – Apply Issue Template to Issue
Apply an Issue Template to an existing Jira issue as part of a Jira Automation rule. This action allows you to enrich, standardize, or complete issues that already exist — without recreating them from scratch.
Use this action when your automation needs to modify an existing issue, not create a new one.
🧩 What This Action Does
When executed, the Apply Issue Template to Issue action:
Applies field values defined in the selected Issue Template to the target issue
Overwrites existing field values where the template defines them
Applies dynamic fields at execution time
Skips fields that are not available or editable in the issue context
Preserves the issue key and identity
This action behaves the same way as using Apply Template manually from the issue view — but is triggered automatically by Jira Automation.
➕ Add the Action to an Automation Rule
To add the action:
Open Project settings → Automation
Create or edit an automation rule
Add a new Action
Select Templify → Apply Issue Template to Issue
The action is now part of your automation flow and will run whenever the rule is triggered.
⚙️ Configure the Action
Select the Issue Template you want to apply using the template picker.
The Issue key field can be left unchanged if you want the action to operate on the issue provided by the automation context.
By default, this field is set to: {{issue.key}}
This means the action will apply the selected template to the issue that triggered the automation rule.
No additional configuration is required.
🧠 Execution Behavior
When the rule runs:
The target issue is identified from the automation context
Template fields are applied to that issue
Dynamic values are calculated at execution time
Fields not present on the issue screen are safely ignored
The issue remains the same entity — only its content is updated.
📌 Typical Use Cases
This action is commonly used to:
Apply structure to manually created issues
Enrich issues after creation based on labels, status, or comments
Standardize issues created by external integrations
React to user actions such as comments or field updates
Apply different templates depending on issue state
📊 Tracking & Visibility
Each execution of this action:
Appears in the Usage History tab of the Issue Template
Shows when and by whom the template was applied
Allows direct navigation to the affected issue
This provides full traceability of automated template usage.
Last updated