Automation step

How to use the Automation step?

Previously, automation via webhooks required technical expertise and the use of APIs.

We have launched a new type of step - Automation step, which enables skipping semi-tech steps to set automation. With just a few clicks, you can save time and reduce human errors by using the Automation feature.

An automation step allows you to perform specific actions on a work item during the approval process.

You can place the automation step anywhere in the approval path. Placing it at the beginning helps prepare the work item for approval, while placing it at the end can, for example, transition it to the next phase.

There are five possible actions in the automation step:

Change work item status

• This action changes the status of a work item. The default option is to select a status from a dropdown list with the corresponding space name or description.

• Alternatively, you can provide the name of the desired status (case-insensitive). This allows for the usage of the same definition for different spaces in which they have a status with the same name, e.g., 'Done'. If no status with that name is found within the space, this step will be skipped.

Change a user assigned to a field

• This action changes the user assigned to a field, such as Assignee, Creator, or Reporter.

Add a comment on a work item

• You can configure the automation to add a comment to a work item. Once set up, a comment will be automatically added after the approval definition runs.

Add/remove label(s)

• Once configured, it will automatically add or remove labels from a work item. You can search for existing labels or create a new one.

Set entity property

Adds an entity property with a specified key and value. You can use work item properties to generate detailed reports on work items that are not covered by Jira's default fields.

To check the entity property, use the following API endpoint:

https://jira-instance1.net/rest/api/3/issue/ISSUE_KEY/properties/ADDED_PROPERTY_KEY

Label condition

The Label condition determines whether this approval step is included in the approval path based on the labels assigned to the work item.

When configured, this step will only be added to the approval path if the defined label criteria are met. You can specify that:

• The work item must include one or more specific label(s), AND/OR

• The work item must not include one or more specific label(s)

If the work item satisfies the configured label condition, the approval step is automatically introduced into the approval path. If the condition is not met, the step is skipped.

Result example

Refer to the example screenshot below of a Jira work item, showing the automation step applied in the approval definition and when it runs.

For more details, including a specific scenario or use case, you can find our blog article here:https://warsawdynamics.com/posts/make-approval-path-for-jira-processes-easier-with-automation/