Sync Magic: Triggering Jira Automation with BPMN Events
Are you tired of carrying out maintenance tasks manually? See how BPMN events spark seamless Jira Automation (opens in a new tab) or your custom microservices.
Create your Jira Automation Rule
Draw your Flower BPMN model including an intermediate throw event
Link the both together by sharing the common webhook Url
Crafting your Jira Automation Rule
Jira Automation allows users to automate common tasks and workflows, reducing the need for manual intervention. This powerful tool enables teams to create specific actions based on predefined conditions and events such as a Flower BPMN event.
You can create a wide range (opens in a new tab) of automated actions, such as:
- Automatically assigning issues to team members based on specific criteria.
- Updating issue fields when certain conditions are met.
- Sending email notifications or alerts.
- Linking issues, creating sub-tasks, or transitioning issue statuses automatically.
Email Automation Example
The screen shot shows a Jira Automation Rule that automatically sends an email as soon as a webhook url is called.
In order to link Flower with this rule, Flower must be provided with the Url.
Therefore, copy the url and then paste it into the corresponding BPMN event as described below.
Fire a Flower Event Trigger
The Flower BPM Engine fires an event automatically while executing a process and invokes a Jira Automation Rule. In a typical flow, an intermediate throw event executes its event (e.g. send a message) once the token has reached it. Once complete, the token continues to all outgoing sequence flows.
To invoke a Jira Automation Rule enter the webhook Url here in the properties panel of the selected event:
Intermediate Throw Events
Any BPMN intermediate throw event is able to fire an event. Which are the following:
| Icon | Event Type |
|---|---|
| None Throw Event | |
| Message Throw Event | |
| Signal Throw Event | |
| Escalation Throw Event | |
| Compensation Throw Event | |
| Link Throw Event | |
| Multiple Throw Event |
Connectivity unleashed: Webhooks and your custom microservices
Flower is the BPM add-on for Jira, so most automation use cases will be within the Atlassian ecosystem and include Jira, Confluence, Bitbucket etc. With Jira Automation, a lot can already be achieved. But of course other services, including your custom microservices, can also be integrated.
Orchestrate Microservices
When entering the event node, Flower calls a HTTP-POST request, that includes the process instance key (FLOWER-375 is the Flower process instance key):
curl -X POST -H 'Content-type: application/json' \
"https://automation.atlassian.com/pro/hooks/xyz" \
--data '{"data": {issues:"FLOWER-375"]}}'The request data body is going to be more flexible in a future version of Flower.