Custom Placeholders

Reusable values shared across all templates.

Custom placeholders let your team define global, reusable values that can be used in any template during cloning.

They work like shared variables and are designed for information that should stay consistent across templates, such as:

  • standard email signatures
  • company legal disclaimers
  • organization-wide contact details
  • internal URLs
  • product or company names
  • etc.

Once configured, custom placeholders can be reused in unlimited templates without redefining their values each time.

How custom placeholders work

Custom placeholders are defined globally in App Settings → Placeholders and managed by Jira administrators.

When a user clones a template:

  • Clone Expert automatically detects all placeholders used in the template
  • If a placeholder matches a configured custom placeholder, its value is automatically prefilled
  • The placeholder is replaced with the configured value during cloning

This guarantees consistency across templates and prevents accidental differences in standardized content.

Important difference vs On-Clone placeholders

Custom placeholders behave differently from on-clone placeholders.

On-Clone placeholders Custom placeholders

Defined directly inside the template

Values are filled manually before each cloning

Ideal for values that change per project or per person
(for example: names, dates, emails)

Defined globally by an admin

Values are predefined and reusable

Intended to be consistent across all templates

Custom placeholders configuration

Custom placeholders can be configured only by Jira administrators.
Configuration is managed in App Settings → Placeholders.

Clone Expert - Custom placeholders

Naming Rules

To avoid conflicts with system objects and Handlebars helpers, these names are reserved and cannot be used:

issue, originalIssue, project, user, now, else, this, date

Additional rules:

  • Only English alphabet letters (A–Z, a–z), digits (0–9), and underscores (_)
  • No spaces
  • No dots (.)
  • No special characters (e.g., -, @, #, $, %, etc.)
  • No non-English letters (e.g., ą, é, ü, ñ, etc.)

 Valid:

{{ClientName}}
{{training_scope}}
{{phase2}}

Invalid:

{{Client Name}} (contains space)
{{client.name}} (contains dot)
{{client-name}} (contains hyphen)
{{firma_żółw}} (non-English letter not allowed)
{{{{nested}}}} (nested braces)

Can custom placeholders be edited during cloning?

Yes but only in a controlled way.

If a template contains a placeholder with the same name as a custom placeholder:

  • The placeholder will appear in the On-clone placeholders panel
  • It will be marked with the “CUSTOM” label
  • Its value will be pre-filled with the global custom value

At this point:

  • The user can modify the value before cloning
  • The change applies only to this single clone
  • The global custom placeholder value remains unchanged

This gives teams flexibility when needed, without breaking global consistency.