# Use dynamic text fields

Templify enables you to define **dynamic content inside text-based fields** of a issue template. Using simple placeholders, you can inject values from other fields into your issue at the moment it’s created.

This feature helps you personalize issue content, increase reusability, and reduce manual editing after applying a template.

***

### 🧩 What Are Dynamic Text Fields?

A **dynamic text field** is a **placeholder embedded inside a text field** (such as *Summary* or *Description*) within an issue template. When a new issue is created from the template, Templify will automatically **replace the placeholder with the value from another field** — based on what was provided or filled during issue creation.

For example, a template Summary might look like:

```
Onboard {Manager Field:user} before {Start Date:date}
```

At the moment the issue is created, Templify will resolve `{Manager Field:user}` and `{Start Date:date}` using the actual values entered or inherited from the template fields — and render the final content accordingly.

***

### ⚙️ How It Works

Dynamic text fields are written using curly braces (`{}`), with the following structure:

```
{Field name:type}
```

* **Field name** — this defines the label shown to users in the dynamic input form when creating an issue from the template.
* **Type** — Specifies the input type that will be showed.

You can use these placeholders in the following fields:

* `Summary`
* `Description`

Before the issue is created from the template, a form will appear prompting the user to fill in the dynamic fields.

***

### ✅ Supported Field Types

Templify currently supports the following types in dynamic text placeholders:

| **Type**    | **Example**               |
| ----------- | ------------------------- |
| `datetime`  | `{Start Time:datetime}`   |
| `date`      | `{Due Date:date}`         |
| `textfield` | `{Title:textfield}`       |
| `user`      | `{Manager:user}`          |
| `select`    | `{Stage:select(Ala,Bob)}` |

> 📝 **Note:** Support for dynamic field types is continuously being expanded.\
> If you need a specific field type that isn’t currently supported, feel free to contact our support.

***

### 🧪 Interactive Demo

The interactive demo below will guide you through:

1. Setting up dynamic text fields inside a template
2. Creating a new issue from that template
3. Seeing how placeholders are replaced with actual field values in real time

{% @arcade/embed url="<https://app.arcade.software/share/oNqJyPBgIeiIsvhimCb2>" flowId="oNqJyPBgIeiIsvhimCb2" fullWidth="true" %}

This is the fastest way to learn how dynamic content works inside templates and how it improves automation and personalization.

***

### 📌 Best Practices

* Use dynamic text in **Summary** to automatically personalize the title of each issue
* In **Description**, combine multiple dynamic fields to generate reusable content blocks
* Always test templates with placeholder syntax to ensure fields match your current configuration
* For better accuracy, use exact field labels — avoid ambiguous names

***

### 🚀 Coming Soon

We’re planning to expand dynamic text field support even further. Upcoming improvements include:

* Additional field types (e.g. multi-select, cascading select, number)
* Support more fields like Environment, any textfield
* Conditional logic (e.g. show/hide text blocks based on selected values)

Templify evolves with the Jira platform — as new field types and APIs become available, we’ll make them fully compatible with dynamic content.

***

####


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://teranoapps.gitbook.io/terano-apps/use-dynamic-text-fields.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.