- Get started
- About
- Quick guide
- Use cases
- Glossary
- Migration
- Configuration
- Global configuration
- Project configuration
- Repository
- Template configuration
- Template scope
- Manage templates
- Supported fields
- Permissions
- Using templates
- Create issue from template
- Create issue structures
- Apply template to existing issue
- Recreate issue
- Use template custom field on issue create screen
- Default templates
- Direct link
- JQL searchers
- Variables
- Static variables
- Dynamic variables
- App Integrations
- Team-managed projects
- Jira Software
- Jira Service Management
- Advanced Roadmaps
- Issue Checklist for Jira
- Advanced
- Automation
- Legacy automation action
- REST API
- Create issue and apply template with Jira REST API
- Security
- Security statement
- App permissions
Legacy automation action
This chapter provides information about Apply template feature in legacy automation.
The Apply Template action is available in legacy automation in Jira Service Management projects.
Automation has many interesting triggers you can use to apply templates, for example: when issue is created, the status has changed or issue has been approved.
To prevent loops in issue created event, delay for newly created issues from template has been implemented and it’s equal 60s.
It means that Apply Template action cannot be executed for issues that were created from or updated by template less than 60s before the action execution.
Unfortunately, legacy automation API has no information about the trigger itself. As a result, we can’t distinguish which trigger is responsible for current execution of the action.
Without the delay, applying a template with subtasks would create infinite loop.
For that reason we don’t recommend using issue created trigger from legacy automation. The same result can be accomplished by using the recommended Apply Template post function.
