Use dynamic fields

Define dynamic values in fields like date or sprint, calculated in real time during issue creation. Automate field population using simple, smart expressions.

Templify enables you to define dynamic values for fields that are calculated and populated automatically at the moment an issue is created. This allows teams to generate context-aware issues without needing to manually enter dates, times, or sprint information.

Dynamic fields bring automation and flexibility to issue creation — especially when combined with reusable templates.

🧩 What Are Dynamic Fields?

A dynamic field in Templify allows you to define a field value that is not static, but instead calculated at runtime, based on the current date, time, user or Jira context. These values are automatically inserted into the issue when the template is applied.

This helps teams:

  • Schedule tasks relative to the current date (e.g. “Due in 5 days”)

  • Automatically assign issues to the current sprint

  • Avoid hardcoding values in templates

⚙️ How It Works

To use dynamic fields in your templates, simply enable the dynamic option for a given field inside the Issue Template panel, and provide a dynamic expression (e.g. now + 5d).

When a new issue is created from that template — Templify will automatically calculate and insert the value into the field based on the expression you've defined.

This happens entirely in the background, ensuring issues are populated with accurate, up-to-date values without any manual input.

✅ Supported Field Types

The following field types currently support dynamic values in templates:

Field Type

Dynamic Support

date

Relative date using now expressions

datetime

Full timestamp calculations

sprint

Automatically assigned by active board

userpicker

Current user creating issue

multiuserpicker

Set od add current user creating issue

assignee

Current user creating issue

🧩 Note: Support for dynamic fields is continuously expanding. If you’d like to request support for a specific custom field type, please contact our team.

🗓️ Date and DateTime Fields

Use the keyword now with optional + or - offsets and time units to define relative time values. Examples:

Expression

Meaning

now

Current date and time

now + 5d

5 days from now

now - 3h

3 hours ago

now + 45m

45 minutes from now

now + 2M

2 months in the future

now + 1y

1 year from now

Supported units: m (minutes), h (hours), d (days), M (months), y (years)

These expressions are resolved at the moment of issue creation and applied directly to supported fields like Due Date, Start Date, or Target Date.

🌀 Sprint Fields

When configuring a template, you can assign the issue to the active sprint on a specific Jira board. Templify will automatically detect the currently active sprint and assign the issue accordingly.

This is especially useful for:

  • Automating backlog grooming

  • Creating sprint tasks from structured templates

  • Aligning new work with your active iteration

👤 User Fields

For fields of type userpicker or assignee, you can set the dynamic value to "Current user". When the issue is created, Templify will automatically insert the account ID of the user who triggered the creation.

This allows you to dynamically assign the issue to the current user — for example, in fields such as Assignee, Manager, or Approver — without manually selecting a user.

👥 Multi-User Picker Fields

For multiuserpicker fields you can choose one of two dynamic modes:

Option
Behaviour

Add creator

The issue creator is appended to any users already defined in the template. Existing assignees remain untouched.

Set creator

The list is replaced so that only the user who creates the issue is stored in the field.

Both options eliminate manual editing and guarantee that the creator is always recorded exactly as required.

🧪 Interactive Demo

The interactive demo below shows how to:

  1. Add a dynamic field to your issue template

  2. Use expressions like now + 7d for due dates

  3. Assign the issue to the active sprint automatically

  4. Create the issue and see how values are filled in real time

This is the easiest way to understand the power of dynamic fields in action.

📌 Best Practices

  • Use relative expressions for dates Employ now ± X to keep due dates, target dates, and start dates automatically aligned with real-world timelines.

  • Leverage sprint auto-assignment Point dynamic sprint fields to the correct board so new issues always land in the currently active sprint—no manual backlog grooming required.

  • Choose the right user mode

    • Set creator for ownership fields (e.g. Assignee) when the issue should belong solely to the reporter.

    • Add creator for collaboration fields (e.g. Watchers, Reviewers) where the creator should be added to an existing list.

  • Reserve userpicker / assignee dynamics for roles that truly follow the creator Avoid overwriting critical allocations (e.g. QA Lead) if they shouldn't default to the person raising the ticket.

  • Combine dynamic fields with default templates Prefill everything—from dates to owners to sprints—so users can submit high-quality issues without touching a single field.

🚀 Coming Soon

We’re actively working to extend support for more field types. Upcoming enhancements include:

  • Dynamic values for more fields

  • Calculated fields using multiple inputs or smart conditions

PreviousUse dynamic text fieldsNextView usage history

Last updated