Description
The Update Issues post function can update one or more issues or sub-taskssubtasks. Issues can be explicitly listed or derived from custom fields or a JQL query. A common example would be to use a JQL query and the Substitution variables substitution variable %jql_result_list%. Regex pattern matching conditions determine whether the issues will be changed or not. The JQL is either run once (default) or once for each issue being updated (when the query contains the %entry% substitution variable).
...
- ISSUE FIELDS - Allow you to define the contents of one or more fields when an issue is updated by this post function. Substitution variables can then be used to populate fields. Issue Fields are grouped into the following common categories:
- Basic Fields - Includes includes fields which are most commonly used when updating an issue in Jira.
- Detailed Fields - Includes includes details associated with the issue, people involved, dates.
- Links - Includes includes details of issue links and link types.
- Comments & attachments - How includes details about how you want to handle comments and specifics associated with attachments.
- Custom Fields - Controls controls whether to copy custom fields and allows you to define values for new custom fields.
- OPTIONAL RULES - Allow you to define the additional criteria for when and how to update the issue(s). Optional Rules are grouped into the following category:
Conditions & Configuration configuration - Define one or more conditions for when to update the issue(s), use JQL to define substitution variables to be used to populate other fields, as well as and set the acting user for updating the issue.
- HELP - Provides quick links to troubleshooting and additional documentation.
Refer to Tutorials for examples.
| Tip |
|---|
|
...