๐Ÿ”ฎ 3 Insider tips for supercharging approvals in Jira Service Management

Spot hero illustrations (Status Page Balloons).png

Approvals are critical for organising many business processes in JSM. But not many people are aware that of some of these hidden tricks to soup up your approval processes.

As a former product manager on JSM, my goal is to share some of these tricks that you can implement today. 

Approvals in slack

With tools such as Slack becoming commonplace, and many users preferring Slack over email for internal communications, being able to approve requests via Slack is a common need for teams.

Although there isn't a way to natively handle approvals in Slack (even when you're using Halp), there is a way to notify approvers using a combination of the official Jira Slack bot and Automation for Jira.

 

Screen Shot 2022-02-09 at 2.18.02 pm.png

This is accomplished by having an automation rule trigger a comment on the issue, and mentioning the approver, which sends a Slack notification to the approver, letting them know there's a request awaiting approval, along with a link to the request on the portal to approve/decline. 

Hi [~accountId:{{issue.Approvers}}] this needs your approval. Please visit {{issue.url.customer}} to approve/decline. 

This is what it looks like in practice:

Screen Shot 2022-02-10 at 11.27.36 am.png

Screen Shot 2022-02-09 at 2.20.41 pm.png

This way the approvers can live in Slack, and not worry about missing any of their approval notification emails. 

 

Manager approvals

A common use case for most business processes (e.g. approving expenses), is to have the manager approve the request.

Because JSM doesn't have a way to natively map a user's manager, a common workaround to accomplish this is to have a user select their manager on the portal, or have the agent manually route the request to the manager for approval.

However, there's now a way to automatically route approvals to managers by setting the manager as the approver dynamically in the workflow.

This is accomplished through a Jira post function:

To use this post function, you'll rely on Multiplier (disclaimer โ€“ I'm one of the founders) - which is an app for Jira that can connect to identity providers such as Okta, Azure Active Directory, Google Workspace and Jumpcloud and automatically fetch the requestor's manager and insert that into your workflow.

When this post function runs successfully on an issue, you'll notice in the issue history that Multiplier has set the approver after issue creation:

Screen Shot 2022-02-10 at 3.48.48 pm.png

 

Approval reminders

Another useful tip is to send reminders to approvers for any pending approvals. 

Using Automation and a little bit of JQL trickery, this is fairly straightforward to accomplish!

First, set up your trigger to Scheduled (once a day).

  • Use the "Run a JQL search and pass results to subsequent conditions and actions" setting. 

    Example JQL: 
    approvals = pending() and ((created < -4d and created > -5d))

 

Screen Shot 2022-02-10 at 9.38.38 am.png

 

The, select Send Email as your action with the following settings.

  • To = Pending approvers

 

Feel free to customize the subject, content and other options to resemble the other notifications your service desk sends out. 

Here are a couple of examples:

  • Subject = Action Required: {{issue.key}} is awaiting your approval
  • Content
    Hello,
    Please review this ticket waiting for your approval.
    To approve or decline this ticket, click the link below: {{issue.url.customer}}

 

Screen Shot 2022-02-10 at 9.59.37 am.png

Here's an example of what this email looks like:

Screen Shot 2022-02-10 at 10.33.21 am.png

Hopefully these tips have been helpful to you, and I would love to hear any other tricks you've implemented in your environment.

Cheers,

Amaresh

1 comment

Comment

Log in or Sign up to comment
Matthias Ortner February 11, 2022

Great! Thanks!

TAGS
AUG Leaders

Atlassian Community Events