...
The value can be a text provided in the Value field of:
- Set field valueissue fields post-function
- Set field value of linked issues post-function
- "User entity properties" of User properties editor page, to copy the value of the specified user property for the current user using Set field value from User Entity Property value post-function
- Set fields of new issue of Create issue post-function to , to set the fields of the newly created issue
- Set fields of one of the Transition issue post-functions, to set fields on the transition screen, if any, in one of the transition issue post-functions
The value can be the result of a Nunjucks template provided in the Value field of:
- Set field valueissue fields post-function
- Set field value of linked issues post-function
- Create issue post-function, to set fields of the newly created issue
- one of the Transition issue post-functions, to set fields on the transition screen, if any
Text value
The value can be specified as text. It can be:
...
You can also inject Nunjucks annotations into the text value. You might also want to look at Accessing an issue or a transition using Nunjucks annotations.
| Info |
|---|
You can use the Set Field Value post-function to clear a field value by leaving the |
...
- String. For example:
"This is a description" - Number. For example:
3.12 - Date. This must be a String containing an ISO_8601 date. For example:
"2016-08-05" - Object. The object must contain at least one field (different from id) which allows the object to be identified unambiguously. For example, a user can be specified as:
{"nameaccountId":"CarteraccountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e"}
For multi-valued fields, the value(s) must be provided as an array of values, even if only one value is provided. For example, to set the Fix Versions field to "2.0": [{"name":"2.0"}]
...