Automation step

1 How to use Automation step?
- 1.1 Change issue status
- 1.2 Change a user assigned to a field
- 1.3 Add a comment on an issue
- 1.4 Add/remove label(s)
- 1.5 Set entity property
2 Result example

How to use Automation step?

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

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

An automation step allows you to perform specific actions on an issue during approval process.

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

There are five possible actions in the automation step:

For other, less common cases, you can refer to webhooks.

Change issue status

This action changes the status of an issue. The default option is selecting status from a select dropdown listed with corresponding project name or description.
Alternatively, you can provide the name of the desired status (case-insensitive). This allows to use same definition for different projects in which they have a status with the same name, e.g. 'Done'. If no status with that name is found within the project, this step will be skipped.

Change a user assigned to a field

This action changes the user assigned to a field of type user or user list such as Assignee, Creator, Reporter, Approvers.

Add a comment on an issue

You can configure the automation to add a comment to an issue. 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 on an issue. 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 issue properties to generate detailed reports on issues 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

For more detailed explanations, refer to the Atlassian documentation.

Result example

Refer to the below example screenshot of Jira issue, 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:Make Approval Path for Jira Processes Easier with Automation · Warsaw Dynamics