By: Andrew Kwatinetz, Product Manager at Azuqua

As you might imagine, we here at Azuqua use our own product to automate many of our internal business processes. From reporting and communication to testing and platform updates, there is no end to the solutions we implement using our own platform. So, when key stakeholders were asking for more timely development project updates, we knew exactly what to do.

We use Jira to track our development schedules, but maybe your team uses Asana, Airtable, Smartsheet, Pivotal Tracker, Trello, or one of the over 200 tools you can also automate using Azuqua. You can easily adapt the solution I built to work for your specific project need

A “FLO” in Azuqua lets you automate a set of tasks, starting with an event — in this case I chose to start the FLO when there is an “Issue Transitioned” event in Jira. This is one of ten different events we currently support for Jira. This one in particular is a webhook, or real-time event, which means Jira runs the FLO immediately each time an issue transitions from one state to another. Alternatively, a “polling event” checks for updates on a schedule, such as every 5 minutes, every day at 9 am, or on a custom schedule of your choice.

 

When the event kicks off, the FLO runs from left to right, starting with the Jira data specific to the event, such as the fields of the issue that was transitioned. You can pass that data to function cards to make decisions and transform it, such as using a Continue If to filter out events you don’t care about and a Compose card to assemble a message that looks exactly how you want it to look. An advanced feature of this Jira event is that you can optionally include JQL (Jira Query Language) to do advanced filtering.

 

One complication with Jira is that epics are stored separately from issues, so the FLO uses a Read Issue action (one of the 31 Jira actions available in Azuqua) to look up the epic name to include in the message. One handy feature of the branching functions in Azuqua such as If/Else is that you can assign different values to use in the next steps of the FLO depending on which branch was run. In this FLO, I assign either the name of the epic or a blank to an output field that gets added to the custom message I build.

 

 

At the very end of the FLO, the composed message is sent to a Slack channel, but I could just as easily send it in email, write values to a spreadsheet, or countless other actions that your process might require.

This whole FLO took me minutes to build and has made an immediate impact on communication across our teams. Just yesterday, one of our Partner Success Managers was able to immediately notify a key partner the very minute a requested fix went live… all with no additional work from me.

You can download a simple version of the FLO I built by clicking here. Connect it to your Jira and Slack accounts, or modify the steps for your specific tools or process. Happy FLO building!

About this FLO:

FLO Name:  Jira Completed Issues to Slack

Connectors: Jira, Slack

Functions: Continue If, If/Else, Assign, List to Text, Compose

Type: Real-time application event

Problem Statement: Our development team uses Jira to track development tasks but key stakeholders outside the team were not always getting timely updates.  

Solution: Using the Jira connector we automated sending important project updates to key stakeholders via Slack in real-time.

ROI: Our Customer and Partner Success Managers get information out to customers more quickly, resulting in higher NPS scores.