Speed up your Jira templates with on-clone placeholders – end-user-friendly smart values

⭐ Introduction

Have you ever wished you could define the values of variables in your Jira templates just before cloning – in a way that applies only to this specific clone operation?

Traditionally, Jira smart values are tied to fields in existing issues. They’re great for Jira Automation, post-functions, and rule-based logic – but they rely on data already stored in Jira.

What if you want the flexibility of smart values…

• but for manually created issues,

• templated work items,

• or fully user-controlled cloning?

This is exactly where on-clone placeholders in Clone Expert for Jira shine.

On-clone placeholders let you build flexible, powerful templates that can be personalized at clone time – even when no source issue exists yet.

And the best part?
Clone Expert automatically detects all placeholders inside your template and prompts you to fill them in the cloning preview panel, exactly where you already adjust names, summaries, hierarchies, and dates.

⭐ Why on-clone placeholders?

Whenever you clone Jira issues from templates, you often need to inject the same contextual information into multiple tasks:

• the new hire’s name

• the project manager

• client contact details

• URLs and environment information

• contract start/end dates

• kickoff dates

• integration credentials

• industry, region, complexity

• team contacts

• compliance or SLA parameters

Filling these manually is:

• ❌ time-consuming

• ❌ frustrating

• ❌ and very easy to get wrong

On-clone placeholders solve this by letting you define customizable variables, such as:

{{NewHireName}}
{{ClientName}}
{{GoLiveDate}}
{{SPOC_Email}}
{{ManagerName}}
{{ContractStart}}

During cloning, Clone Expert for Jira automatically scans all placeholders and displays them in the preview panel, asking you to provide values for THIS specific cloning activity.

After cloning, all placeholders are replaced across:

• Summaries

• Descriptions

• Text custom fields

• Subtasks

• Checklists or acceptance criteria

Your template becomes instantly personalized – without manual rewriting.

⭐ Example 1: New Hire Onboarding

The onboarding process is one of the most common repeatable workflows inside HR teams – and one of the easiest to automate with on-clone placeholders.

In a previous article, we covered how to build a basic onboarding template using native Jira functionality. Now, let’s improve it using on-clone placeholders.

Why placeholders are perfect for onboarding

Every onboarding process repeats the same pieces of data:

• new hire’s name

• private email

• hiring date

• manager’s name

• buddy or mentor

• account setup details

Instead of rewriting “John Doe” a dozen times, simply define:

Example EPIC and tasks

Epic:
[TEMPLATE] {{NewHireName}} – Hiring & Onboarding

Tasks:
[TEMPLATE] {{NewHireName}} Define agreement details
[TEMPLATE] {{NewHireName}} Medical Checks

Subtasks:

Issue a referral for medical examination
Verify medical clearance

[TEMPLATE] {{NewHireName}} Prepare employment contract
[TEMPLATE] {{NewHireName}} Send documents for signature

Subtasks:

Gather internal signatures
Collect signed documents from {{NewHireName}}

[TEMPLATE] {{NewHireName}} Announce new hire internally
[TEMPLATE] {{NewHireName}} Assign buddy

Placeholders in descriptions

You can combine multiple placeholders inside long-text fields:

Description example:

Prepared documents must be sent to {{NewHireName}} ({{NewHirePrivateEmail}})
at least 1 week before {{HiringDate}}.
Notify {{ManagerName}} once the package has been delivered.

During cloning, simply enter

• NewHireName → John Doe

• NewHirePrivateEmail → john.doe@example.com

• HiringDate → 2025-03-01

• ManagerName → Sarah Johnson

And your entire onboarding workflow becomes instantly personalized — across all issues.

⭐ Example 2: New Client Implementation

Client onboarding and implementation processes are highly repeatable, but very data-heavy. They often require:

• customer contacts

• environment URLs

• integration details

• licensing information

• SLA parameters

• contract dates

• kickoff information

On-clone placeholders allow you to recreate the entire context of a new implementation project in seconds.

Useful placeholders for client onboarding

Contact details

{{SPOC_Name}}
{{SPOC_Email}}
{{SPOC_Phone}}
{{SME_Name}}
{{SME_Email}}
{{SME_Phone}}

Contract & documentation

{{documentation_URL}}
{{contractStart}}
{{contractEnd}}

Client details

{{ClientName}}
{{ClientShortName}}
{{ClientIndustry}}
{{ClientLocation}}
{{ClientSize}}

Project & environment

{{ProjectName}}
{{EnvironmentURL}}
{{GoLiveDate}}
{{KickoffDate}}
{{ImplementationPhase}}
{{NumberOfUsers}}
{{TrainingScope}}

Integrations

{{Integration_CRM}}
{{Integration_ERP}}
{{APIKey}}
{{LicenseKey}}
{{WebhookURL}}

{{SupportTier}}
{{SLA_ResponseTime}}
{{SLA_ResolutionTime}}

⭐ Example client implementation template

Epic

[TEMPLATE] {{ClientName}} – New Client Implementation

1. Kickoff & Alignment

[TEMPLATE] {{ClientName}} Kickoff meeting preparation

Subtasks:

• Prepare kickoff agenda

• Send materials to {{SPOC_Name}}({{SPOC_Email}})

• Confirm attendance for {{KickoffDate}}

2. Access & Environment Setup

[TEMPLATE] {{ClientName}} Environment provisioning

Subtasks:

• Provision instance at {{EnvironmentURL}}

• Set access for {{SPOC_Name}}

• Generate API key: {{APIKey}}

• Validate license: {{LicenseKey}}

3. Requirements & Configuration

[TEMPLATE] {{ClientName}} Requirements gathering

Subtasks:

• Review workflows for {{ClientIndustry}}

• Confirm integrations: {{Integration_CRM}}, {{Integration_ERP}}

• Prepare configuration draft for {{SME_Name}}

4. Data Migration

[TEMPLATE] {{ClientName}} Data migration preparation

Subtasks:

• Validate datasets

• Map fields

• Plan migration before {{GoLiveDate}}

5. Training

[TEMPLATE] {{ClientName}} Training sessions

Subtasks:

• Prepare training materials based on {{TrainingScope}}

• Schedule training for {{SPOC_Name}} and {{SME_Name}}

• Create documentation space: {{documentation_URL}}

6. Go-Live Validation

[TEMPLATE] {{ClientName}} Final go-live review

Subtasks:

• Confirm readiness checklist

• Verify integrations

• Match support tier: {{SupportTier}}

• Official go-live on {{GoLiveDate}}

7. Post-Go-Live Support

[TEMPLATE] {{ClientName}} Hypercare phase

Subtasks:

• Monitor usage

• Review SLAs ({{SLA_ResponseTime}}, {{SLA_ResolutionTime}})

• Weekly sync with {{SME_Name}}

• Document findings in {{documentation_URL}}

⭐ Final thoughts

On-clone placeholders transform static Jira templates into adaptive, reusable workflows that automatically personalize themselves for each cloning activity.

With Clone Expert for Jira, they help teams:

• avoid manual rewriting

• improve accuracy and consistency

• speed up project setup

• standardize workflow execution

• reduce onboarding and implementation time

• empower end-users to clone templates without mistakes

Whether your teams run onboarding processes, repetitive operational tasks, client implementations, audits, approvals, or migrations, on-clone placeholders save hours every single week.

⭐ Want to explore more?

On-clone placeholders are part of Clone Expert for Jira, the templating & cloning solution used by teams to build scalable, repeatable Jira workflows.

🔗 Clone Expert for Jira on the Atlassian Marketplace

📘 Documentation (Getting Started, examples, configuration)

🎥 Want a personalized walkthrough?

If you’d like to see on-clone placeholders in action or want help designing your templates, feel free to reach out. I’d be happy to show you more.