nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automate an Approver based on Workflow Approval Process

John Lombardo_k1rg0g

Hello,

We have a Workflow that involves getting approval in order to move onto the next stage of the Workflow.

Is there a way to automatically assign the approver using Jira Automation or another means? I have tried to setup an Automation user the Approver field as shown in the picture below, but it is not assigning the approver where the Work Flow will accept that approval and move forward to the next step in the flow.

jira automation.PNG

This automation puts an approver in the details column, but the Workflow is still saying an approver needs to be selected.

Is there a way to make the automation fill in an approver for Workflow approval?

Accepted answers

Ste Wright

Hi @John Lombardo

This looks like a Team-managed Project, correct? As far as I know, it won't use the standard "Approvers" field which Jira has out of the box.

AFAIK it uses a special Approvers field which is part of the Workflow - you can also create custom Approver fields...

Go to Project Settings > Request Types
Select a request type which includes the approval step in the workflow
Press Edit Workflow
Select the status where the approval is required
Select the approval rule
Click Next
Select the "Approver field" section
Type in a different word - eg. Approvers Custom - and it'll give you the option to create a new "approver" custom field, which can be added to the agent screen

...but even with a new custom field and its ID (I got this via https://<your domain>.atlassian.net/rest/api/3/field), and the rule successfully populating the user, it still doesn't add it the Approvers section.

I'd contact Atlassian Support and get some clarity on how those fields work. If you do contact them, let us know how it goes

Ste

All comments

Mikael Sandberg

Hi @John Lombardo,

Welcome to Atlassian Community!

If you look at the warning message it is expecting a user to be added to the Approver field, not the Approvers. So It looks like you have two or more fields for approvers.

John Lombardo_k1rg0g

Hi @Mikael Sandberg

Thanks!

Yes I added that field after I couldn't find where in Jira Automation to add an approver to the Approver Field inn the workflow approval. I was hoping if I added Approvers to details it would populate.

Is there a way to do this?

Mikael Sandberg

The approver field should be like any other fields, just use the edit issue component in the automation to add them. It is not showing up as an option then you can always use the advanced option to update the field, something like this:

{
  "update": {
  "customfield_12345": [{
    "add": {
      "id":"<Atlassian Id>"
      }
    }]
  }
}

Note that when you do it via the advanced option you have to use the Atlassian Id for the user that you want to add as the approver.

John Lombardo_k1rg0g

Thanks. I will test and follow up.

Ste Wright

Hi @John Lombardo

This looks like a Team-managed Project, correct? As far as I know, it won't use the standard "Approvers" field which Jira has out of the box.

AFAIK it uses a special Approvers field which is part of the Workflow - you can also create custom Approver fields...

Go to Project Settings > Request Types
Select a request type which includes the approval step in the workflow
Press Edit Workflow
Select the status where the approval is required
Select the approval rule
Click Next
Select the "Approver field" section
Type in a different word - eg. Approvers Custom - and it'll give you the option to create a new "approver" custom field, which can be added to the agent screen

I'd contact Atlassian Support and get some clarity on how those fields work. If you do contact them, let us know how it goes

Ste

John Lombardo_k1rg0g

Following up on this. The Automation did not work, but it was a team-managed project. Not sure if that effects it.

I made the desk a company-managed project, like it should have been, and the automation works as intended

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management