...
...
...
...
Description
The Update Issuesissues 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 the 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).
The configuration of this post function is streamlined by grouping all configuration settings into various tabs for easy access:
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 -
Includesincludes fields
whichthat are most commonly used when updating an issue in Jira.
Detailed Fields -
Includesincludes details associated with the issue, people involved, and dates.
Links -
Includesincludes details of issue links and link types.
Comments &
Attachments - Howattachments - includes details about how you want to handle comments and specifics associated with attachments.
Custom Fields -
Controlscontrols 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
toto troubleshooting and additional documentation.
...
| Tip |
|---|
|
| Info | ||
|---|---|---|
| ||
Only custom fields can be updated on the create issue transition; standard fields cannot be updated on the create issue transition. This is a permanent restriction - see CW-34. |
Example
This scenario introduces a new Update issue workflow post function to a transition step within an existing workflow.
Background
This scenario uses an example ePub workflow that helps teams coordinate the publication of electronic books. While transitioning from the "Open" to "In Draft" steps, let us create a new sub-task within a specific IT Services project in the Jira instance. This creates a sub-task issue in the backlog of the Digital Publication team, so their manager can begin to forecast and assign resources.
Steps
...
| border | 0 |
|---|---|
| heading | 0 |
| multiple | false |
| enableHeadingAttributes | false |
| columnAttributes | style="border:0;width=5%;",style="border:0;width=65%;",style="border:0;width=30%;max-width=30% !important;" |
| id | steps_table |
| enableSorting | false |
| enableHighlighting | false |
...
...
Select Post Function
- Click the Add Post Function button in the Post Functions section of the workflow transition you want to add post function to.
- Find and select the Update Issues in the list.
- Click the Add button to add details to the post function.
...
...
Add Details to Update Issues
- Enter "HOT:%original_summary%" in the Summary field.
- Select the Detailed Fields tab.
- Perform the following:
- Select "Original key" from the available option in the Issues to Update field.
- Enter "HOT:%original_labels%" in the Labels field.
- Retain "Same" in the Resolution and Reporter fields respectively.
- Select the Conditions & Configuration tab under OPTIONAL RULES.
- Perform the following:
- Enter "%original_priority%" and "Blocker" in the Condition 1 and corresponding Regular expression pattern fields respectively.
- Enter "%original_components%" and ".+" in the Condition 2 and corresponding Regular expression pattern fields respectively.
- Click the Add button to save the values.
...
Publish and view post function
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|