Placeholders

Placeholders in our application serve as dynamic variables, bringing high flexibility and customization to your templates. These placeholders can be utilized in any text field, such as descriptions or summaries, automatically inserting relevant values. With common standard placeholders like {SUMMARY}, {DATE}, and {CUSTOM_FIELD_12345}, you can streamline the template creation process. Moreover, our app allows you to define and use custom placeholders, tailoring your templates to meet specific needs and workflows.

How Placeholders Work

Placeholders in your template automatically fill in with real data when you clone an issue. When you add placeholders like {SUMMARY} or {DATE} and then hit the Clone button, these placeholders get replaced with the actual information relevant to the issue. This means you can set up your templates with placeholders beforehand or add them during the cloning process, making managing your templates easier and more efficient.

Supported Fields

You can utilize placeholders in the following fields and custom field types within your templates:

Summary
Description
Environment
Custom Fields with text types:
- Short Text
- Paragraph
(Comming soon!) Comments

How to start

Populate your epic and linked issues with placeholders, or add them later in the template clone form.

2. Examine your template data and utilize the Placeholders drawer to view available placeholders.

3. Once cloning is complete, placeholders will automatically be replaced with their actual values.



Tip

The placeholders cheat sheet is available under the Placeholders button in the clone window.

You can see all standard and custom placeholders that can be used on the list — more about available placeholders in the next chapters.

Standard placeholder

Here is a list of all standard placeholders that are available in the tool after plugin installation in your Jira instance:

Syntax	Description	Example
`{SUMMARY}`	Summary of the issue	Issue summary
`{DESCRIPTION}`	Description of the issue	Issue description
`{PARENT_ID}`	Parent issue id. For subtask, it is the parent issue id. For the issues in the Epic, it is the epic issue id. For epic issue, it is empty.	12345
`{PARENT_KEY}`	Parent issue key. For subtask, it is the parent issue key. For the issues in the Epic, it is the epic issue key. For epic issue, it is empty.	ABC-123
`{PARENT_SUMMARY}`	Parent issue summary. For subtask, it is the parent issue summary. For the issues in the Epic, it is the epic issue summary. For epic issue, it is empty.	Epic summary
`{PARENT_DESCRIPTION}`	Parent issue description. For subtask, it is the parent issue description. For the issues in the Epic, it is the epic issue description. For epic issue, it is empty.	Epic description
`{CURRENT_USER_ACCOUNT_ID}`	Current user account id.	12345:6789
`{CURRENT_USER_NAME}`	Current user name.	John Doe
`{ASSIGNEE_ACCOUNT_ID}`	Assignee account id.	98765:4321
`{ASSIGNEE_NAME}`	Assignee name.	Richard Roe
`{ORIGINAL_REPORTER_ACCOUNT_ID}`	Original reporter account id.	56789:1234
`{ORIGINAL_REPORTER_NAME}`	Original reporter name.	Jane Smith
`{PROJECT_ID}`	Project id.	12345
`{PROJECT_KEY}`	Project key.	ABC
`{PROJECT_NAME}`	Project name.	My Project
`{ORIGINAL_ESTIMATE}`	Original estimate.	1d 2h 3m
`{DATE}`	Current date.	2021-01-01
`{TIME}`	Current time.	12:00
`{DATETIME}`	Current date and time.	2021-01-01 12:00
`{CUSTOM_FIELD_12345}`	Value of the custom field with id 12345. Replace 12345 with the id of the custom field you want to use. You can find the id of the custom field following the article here.	Custom field value

Custom Placeholders

Our plugin extends its functionality by allowing you to create custom placeholders and use the standard ones. Here’s how you can set them up:

Go to Apps → Template (Epic) Cloner → Placeholders.
Click the Create button beneath the custom placeholders table to start defining your placeholders.
Custom placeholder names should be composed of uppercase letters, numbers, underscores (_), or periods (.).
You can even combine custom placeholders with standard ones for more versatility.
Once created, these custom placeholders are accessible to all Jira users during the cloning process, enhancing template customization.
Remember that only users with admin privileges can add, modify, or delete these custom placeholders.

Access and Permissions

Users with admin access can create/edit/delete custom placeholders.
Users can view and use custom and standard placeholders in the clone template form without admin access.
A helpful panel in the clone template form displays available placeholders for ease of use – available for all users.