Placeholder syntax update – action required⚠️

Note

Read it carefully if you have already been using placeholders in a format with just one bracket {}

This update does not introduce placeholders from scratch — it replaces an older, limited implementation with a more flexible and unified placeholder system.

Clone Expert for Jira has introduced a new placeholder engine.
As a result, the old placeholder formats no longer work and must be replaced.

If your templates still use the legacy placeholders listed below, they will not be resolved during cloning. Instead, they will remain as plain text.

What you need to do

  1. Open your existing templates.
  2. Find placeholders written in the old format (single braces, uppercase names).
  3. Replace them with their new equivalents (double curly braces, object-based syntax).
  4. Save the template.
  5. That’s it. No reconfiguration, no admin actions required.

Placeholder mapping table

Use the table below to migrate your templates.

Old placeholder

New placeholder

 
{SUMMARY}
 
{{originalIssue.summary}}
 
{DESCRIPTION}
 
{{adfToWikimarkup issue.description}}
 
{PARENT_ID}
 
{{originalIssue.parent.id}}
 
{PARENT_KEY}
 
{{originalIssue.parent.key}}
 
{PARENT_SUMMARY}
 
{{originalIssue.parent.summary}}
 
{PARENT_DESCRIPTION}
 
{{originalIssue.parent.description}}
 
{CURRENT_USER_ACCOUNT_ID}
 
{{user.accountId}}
 
{CURRENT_USER_NAME}
 
{{user.displayName}}
 
{ASSIGNEE_ACCOUNT_ID}
 
{{originalIssue.assignee.accountId}}
 
{ASSIGNEE_NAME}
 
{{originalIssue.assignee.displayName}}
 
{ORIGINAL_REPORTER_ACCOUNT_ID}
 
{{originalIssue.reporter.accountId}}
 
{ORIGINAL_REPORTER_NAME}
 
{{originalIssue.reporter.displayName}}
 
{PROJECT_ID}
 
{{project.id}}
 
{PROJECT_KEY}
 
{{project.key}}
 
{PROJECT_NAME}
 
{{project.name}}
 
{ORIGINAL_ESTIMATE}
 
{{originalIssue.timetracking.originalEstimate}}
 
{DATE}
 
{{now.jiraDate}}
 
{TIME}
 
{{now.shortTime}}
 
{DATETIME}
 
{{now.jqlDateTime}}
 
{CUSTOM_FIELD_12345}
 
{{originalIssue.customfield_12345}}

Where to find the full placeholder list

The most up-to-date list of supported placeholders and mappings is always available:

👉 In clone window
Click Placeholders in the cloning dialog

This ensures you are always working with the current, supported syntax.

Why this change happened

The new placeholder system:

  • uses one consistent syntax ({{ }})
  • aligns with Jira Automation smart values
  • supports functions, formatting, and logic
  • works across local, custom, and object placeholders

Summary

Old placeholder formats are no longer supported

  • All templates must use the new {{ }} placeholder syntax
  • Migration is straightforward using the built-in mapping table
  • The change enables more powerful and reliable template behavior
  • If you maintain shared or critical templates, we recommend updating them promptly to avoid unexpected results during cloning.

Need help with the migration?

If you have existing templates and want to ensure your placeholders are updated correctly, you don’t have to figure this out on your own.

📅 Book a short call, and we’ll walk through your templates together:
Clone Expert for Jira – Calendar

📧 Or contact us directly at:
jira.support@vilisoft.com

We’re happy to help you validate your placeholders, answer questions, or review more complex template setups.