Previously, Automation automation via webhooks required technical expertise and the use of APIs. We have launched new feature called ‘Automation’ which enables us 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!
You can place the automation step at any place in the approval path. With the automation step at the beginning, you can prepare the page for the approval process. If placed at the end of the process, you could for example transition the page to the next phase.
An automation step allows you to perform an action on a page.
...
There are four actions available:
| Info |
|---|
For other, less common cases, you can refer to webhooks. |
...
Change page status - This action changes the status of a page and offers two options.
Space suggested status - the user can provide the name of the desired status. If no status with that name is found, this step will be skipped.
Custom status - As custom statuses are user-specific. , You need to provide a name, and we'll match it with the statuses available to the user who started the approval, or create a new one for them. Alternatively, you can select a user, choose one of their statuses, or provide a new one. The custom status will be added by the selected user. If you provide a custom status that does not yet exist, you can also select its color. The default color is blue.
...
Add a comment on a page - Adds a text comment to a page.
...
Add/ remove label(s) - Adds or removes a label on a page.
...
Set entity property - Adds an entity property with a specified key and value. Advanced Reporting and Filtering - you You can use issue page properties to generate detailed reports on issues pages that are not covered by JiraConfluence's default fields.
...
To check the entity property, use the following API endpoint:
...