Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Adding Multiple users for Approval with automation Edited

I am using Automation for Jira in JSM Cloud. I need to have a field drop down be able to be selected and each time a value is selected it then add an approver to the approval field. So if 5 values selected it will then add 5 different users as approvers.

Each value in drop down is a department and each department as a representative that is the approver.

I am using the if else for each value to make the change to the approver field but it seems it will only add on approver to the field not multiple.

Anyone else have this before. I have all approvers selected in the approval process.

3 answers

1 accepted

0 votes
Answer accepted

Often when configuring approval Flows, we typically pull the manager information from a user’s profile and assign the approval task to said manager. This is a typical use case for a vacation request form. However, this is not always the use case where approver details are static.



I agree with you. I usually create automation for approvals but in this case there is a total of 15 departments that are being request to approve with 15 approvers which will make this a total of 225 outcomes in an automation. I can't see any other way to do this other then making those edits in a if else statement. I think that would be rather to much and I have moved to ask the stakeholders to ask the users to add appropriate approver or have a agent add the approvers base on a matrix. I am not sure how else to do this in this situation. I believe that they are asking Jira to do something it is not able to do.

@William Atkins , I have a use case to add the requester's manager as an approver when a ticket is created. 

Can you please let me know if you are using any webhooks to achieve this? 

Like Aaron Geister likes this

no webhook. I have configured this a different way and allowed the users to pick the respective users to add to the issues as approvers.

I figured that if I did this with automation I would need 225 variation to make it work correctly based on the field selection.

image.pngI was thinking that this would add each users based on the if else but its only allowing the edit of issue to be one users as approver. I need it to add each person as an approver.

Hello @Aaron Geister 


If you need to add multiple approvers in the same status, select the option below. (Remember that your approver field must be multiple users)

Captura de tela 2021-06-16 133343.png


Then, you can use the "Consider approved after"

→ All aprovals - all your users MUST approve the issue, however, even if approved by any user, the issue will be pending approval until EVERYONE approves it. (complicates life for approving users)

N approvals - in this you can set the number for approval. Example: if you have 5 approvers and the limit set for 3 approvals, 2 approvers deny and 3 approve, your issue will be approved). (But it is also in the queue for those who have already approved the issue.)


Using the best pratices, if each person must be approve, increase your workflow to supports more steps to approvals :)

This is what I have told the stakeholders. To have multiple step approval but they want to automate the approval process and get all people who approve to just get the approval notification and approve.

I have it set to all approve at this time but I can not get the automation to push to add more approvers based on the field selected.

Commercial = approve 1

Tech =  approval 2

In the automation I am adding Affect group values and then adding the person that is suppose to be the approver to the list of approvers. It is editing the approvers but only adding one approver. I need it to add all approvers to the approval field.

To make this simplier in idea is that they don't want people to remember who the approver is and add them to the field they want a field selected and the automation add the users to the approval. Hope this makes sense.

What would be the impact of defining the sequence of approvers based on areas like you mentioned, commercial, tech etc?
It will be easier to define the approvers in each step as reuse the same field in all the steps.
The advantage of using different statuses is that you can define SLA's even for each step of your process, this way you can know who delayed the process or not :)

Like Aaron Geister likes this

I agree with you but the stakeholders do not agree with us. SLA is only important to them for the first response and they want a process that is automated for the approval of the issue so its less thought to the user requesting the change.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Atlympic Event: Jira Service Managemnt

Hello Community!  Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...

205 views 1 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you