
Documentation
Issue Templates & Recurring Tasks for JiraBrowse
Documentation
Issue Templates & Recurring Tasks for JiraVariables
Variables keep a template from going stale. Write {{date+7d}} as a due date once, and every work item made from the template is due a week after it's created.
Inserting a variable
- Put the cursor in the summary, the description, a field or a child item.
- Click the { } button in the editor toolbar.
- Pick a variable. The list shows an example of each.
You can also type them by hand.
The variables
| Variable | Becomes |
|---|---|
{{user.name}}, {{user.email}} |
The person creating the work item (email where their profile allows it) |
{{assignee}}, {{reporter}}, {{priority}}, {{labels}} |
What the template itself sets |
{{project.key}}, {{project.name}} |
The space |
{{issueType.name}} |
The work type |
{{requestType.name}} |
The portal request type, on a service space |
{{date}}, {{date.long}}, {{time}} |
Today, as 2026-10-27 or October 27, 2026, and the time |
{{weekday}}, {{month}}, {{year}}, {{week}}, {{quarter}} |
Parts of today's date |
Date offsets
Add days, weeks, months or years to a date variable:
{{date+7d}} a week from today
{{date+2w}} in two weeks
{{date+1m}} next month
{{date-1d}} yesterday
{{date.long+7d}} a week from today, written out
Good to know
- Dates use the time zone in the Jira profile of the person creating the work. Scheduled work uses the schedule's time zone.
- A variable the app doesn't know, such as
{{proj.key}}, stays as written, so a typo is easy to spot. - To ask for a value instead, use a fill-in question.
Related
Stuck on something this page does not cover? Ask the developers.