...
Note | ||
---|---|---|
| ||
If you insert a Post-function in the Create transition, you must make sure that you move it down to place it:
In general, when using a post-function in the Create transition, if it doesn't work as expected, try moving it around the Creates the issue originally built-in function. Also, please note that any field based on issue links (such as some of those created by the Tempo plugin) are not available during the Create transition (because issue links are created after the initial issue creation). |
Info | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Several of the following post-functions support conditional execution, in the way of an optional Groovy expression that must return This Groovy expression can reference any field value of the current issue. Access to issue field values is achieved by the following syntax:
where <field_ID> is a built-in JIRA field ID (see this list) or a custom field ID (in the form For complex conditions, you can also access the JIRA Issue object directly using the Finally, you can use the
|
...
- Property key: defaultAssignee
- Property value: contains a comma-separated list of entries in the form ProjectKey -> *RoleName. *For example:
TST -> Developers, JMWE -> Testers |
For backward compatibility, the following two forms are also supported:
...