SupportBook a demoExplore the apps
Templates · · 2 min read

Variables in Jira templates: fill in what changes

Variables let one template set serve every run: today's date, the space, the reporter, a new hire's name. Here are the ones we use most.

A template is only useful if it fits every time you use it. The parts that change, like a date, a name or a space, are where templates usually break. Variables fix that. You write the placeholder once, and the app fills it in when the template set runs.

How variables work

In AppsDelivered Templates, a variable starts with a dollar sign, such as $today. You can put variables in a work item’s summary or description, and in other single-line and multiline text fields. When the template set runs, each variable is replaced with its value.

There are two kinds:

  • System variables fill themselves in, like today’s date or the space key.
  • Custom variables are ones you define, like $NewEmployee. The app asks for the value when you apply the set.

System variables we use most

Variable What it fills in
$today Today’s date
$tomorrow Tomorrow’s date
$nextWeek The date a week from today
$datetime The date and time the set runs
$projectKey The key of the space the work item is created in
$projectName The name of that space
$username The person who applied the template set
$parentSummary The summary of the parent work item

The full list is in our documentation. Some names still say project from Jira’s older wording. They work in spaces the same way.

Custom variables

Custom variables are for what only you know at run time. A few examples:

  • $NewEmployee in every work item of an onboarding set, so each work item reads “Order a laptop for Dana Ortiz”.
  • $advisory in a patch rollout, so the epic reads “Patch rollout, CVE-2026-1234”.
  • $version in a release checklist.

You can also add a user variable to the Assignee field. The app asks who should get the work, and every work item that uses the variable goes to that person.

A few habits that help

  1. Name variables for people, not for code. $NewEmployee is clearer than $ne1.
  2. Put the variable early in the summary. “Access review, $today” sorts and searches better than “$today access review” in most lists.
  3. Test the set once on request before you schedule it. You see exactly what each work item will say.

Variables are the difference between a template you copy and fix, and a template you apply and trust.

Riley Venable co-founded AppsDelivered in 2017 and leads its engineering as CTO. He builds the Forge apps behind AppsDelivered Templates, Comments and Feeds. More about Riley

All posts
Templates ·

New hire onboarding in Jira with one template set

Templates ·

Recurring work items in Jira Cloud: your options

Templates ·

A Jira release checklist you build once