| Section |
|---|
| Column |
| Excerpt |
A variable looks up a value from the template context. This documents details on the variables available in JMWE and how to create custom variables. |
If you want to insert the value of a variable in your template, you can use the following syntax: {{ myVar }}. This looks up for the myVar variable from the context and displays it. Variable names can have dots in them which look up properties, just like in javascript.
...
| width | 400px |
|---|
...
...
On this page:
| Table of Contents |
|---|
Variables available in JMWE
JMWE makes the issue, transition, linkedIssue, parentIssue, now and currentUser variables available to templates. You can access their properties using "." or "[ ]". For example, you can access the current issue key using {{issue.key}}.
issue variable
The issue variable is used to insert data of the issue being transitioned. You can access the issue data by looking up at its properties.
...
The nowObj variable represents now138446514 as a Moment.js object.
For example:
{{ nowObj }} returns now 138446514 as a Moment.js object.
{{ nowObj | date }} returns current date as a date Object
{{ issue.fields.duedate | date('clone') <= nowObj }} returns true if the ticket is overdue.
User-defined variables
In addition to the above variables, you can also create your own variables within the template using the set Nunjucks tag.
For example:
{% set x = "High" %} sets the value of the variable x to High. You can also set the variable to an object. For example: {% set assignee = issue.fields.assignee %}