Wiki
Clone wikiThe Scheduler / cloud / latest / Predefined values in any issue fields
Predefined values in any issue fields
The Scheduler has predefined variables which can be used in any text field. When Scheduled Issue is fired these variables are converted to the corresponding values:
| Variable | Meaning | Examples |
|---|---|---|
${fireCount} |
Fire count | 5 |
${createdDate} |
Creation date in format YYYY-MM-DD HH:mm timezone | 2017-02-02 14:41 Europe/Warsaw |
${createdDate.day} |
Creation day | 2 |
${createdDate.month} |
Creation month | February |
${createdDate.shortMonth} |
Creation month in number form | 2 |
${createdDate.year} |
Creation year | 2017 |
${createdDate.date} |
Creation date in format YYYY-MM-DD | 2017-02-02 |
${createdDate.time} |
Creation time in 24 hour format | 14:41 |
${createdDate.timezone} |
Creation date timezone | Europe/Warsaw |
${createdDate.timezoneOffset} |
Creation date timezone as time offset | GTM+01:00 |
${createdDate.weekOfMonth} |
Creation date week of month | 2 |
${createdDate.weekOfWeekYear} |
Creation date week of week-based-year (see below) | 28 |
${createdDate.weekYear} |
Creation date week-based-year (should be used with .weekOfWeekYear) | 2017 |
${dueDate} |
Due date in format YYYY-MM-DD | 2017-02-02 |
${dueDate.day} |
Due date day | 2 |
${dueDate.month} |
Due date month | February |
${dueDate.shortMonth} |
Due date month in number form | 2 |
${dueDate.year} |
Due date year | 2017 |
${dueDate.weekOfMonth} |
Due date week of month | 2 |
${dueDate.weekOfWeekYear} |
Due date week of week-based-year (see below) | 28 |
${dueDate.weekYear} |
Due date week-based-year (should be used with .weekOfWeekYear) | 2017 |
Example
You can use these variables as shown below:
When the actual issue gets created, the result looks as follows:
Updated