- 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
Last updated Sep 20, 2021
Old view vs. new view
This chapter provides information about possible errors occurring in dynamic variables in the new issue view.
With introduction of the new issue view, defining dynamic variables may be tricky. The main disadvantage is that the new editor omits or adds extra characters like [, {, that are crucial for dynamic variables to work. For example [variable] becomes \[variable].
If you notice that your variables are not replaced correctly, switch to the old issue view and remove/add extra slashes (or other characters) in your placeholders.
Make sure your field is added to Template fields. Dynamic variables are parsed and replaced only in fields added to the scope.