---
title: "Setting Custom Approvers via Post function"
canonical: "https://helpcenter.mindproapps.com/space/SDC/2347731125/Setting%20Custom%20Approvers%20via%20Post%20function"
format: markdown
---
> ℹ️ **Summary: **Learn how to set custom approvers in your workflow using our dedicated post-function.

### **Setting a Custom Approval via Post-function**

 

Besides the option to set automatic Issue Approvals based on the user hierarchy defined in the Identity Provider (IdP), Mindpro Sync has a dedicated post-function that can be added to your JSM workflow to set pre-selected approvers during a status transition.

---

### **How to add the Mindpro Sync Post function**

 

To configure the Mindpro Sync post function to set the custom approvers, please follow the steps below:


- Navigate to Project settings > Workflows
- Select the workflow you'd like to use and click Edit > Diagram
- Click on the transition upon which the IdP data should be updated.
- Open the "Post Functions" option, and on the next screen, click on the "Add post function" link
- In the "Add Post Function to Transition" screen, select and add the option "**Mindpro Sync: Assign Issue Approvers**."
- In the "Administration" screen, select "Approvers" and choose the Jira users to be the "Issue Approvers" (You can add more than one approver if required ).
- Click on the "Publish Draft" link to save the workflow changes.

![Mindpro-1722611992461-1x.png](media://96fff146-35bc-4fa6-90cb-b64090832a39)


> ℹ️ **Good to know**
> ℹ️ 
> ℹ️ After the post function is added, whenever you use that transition in a issue, the system will automatically add the related user as the issue approver. No additional configuration is needed.

---

### **Changing from “Hierarchy” to “Post function” Approvals**

 

Mindpro Sync allows you to choose between two options to set issues approvers, you can choose between the option based on the Hierarchy of users ([see more here](https://mindpro.atlassian.net/wiki/spaces/SDC/pages/2347730696)) or this option above via the Post function. 


In case you have the approver previously set by the Hierarchy and you move your workflow with a transition that also sets the approver (via post function), there are 2 expected behaviors:


**1) IF** the approver from the post function is the same person previously set by the Hierarchy **THEN **the system will understand this is the same person and will not do anything. The "approvers" field will keep with the same original approver.


**2) IF** the approver from the post function differs from the one previously set by the Hierarchy** THEN** the system will add this as an additional approver, and the "approvers" field will now have two approvers.


This means this post-function will never delete or replace people previously set on the "approvers" field like it is optionally done using the[ auto-assignment for approvals](https://mindpro.atlassian.net/wiki/spaces/SDC/pages/2347730696/Configuring+the+approver+auto-assign#Enable-auto-assign-approver-based-on-user-hierarchy). This is especially useful if other apps also populate this field. 


> ℹ️ **Keep in mind**
> ℹ️ 
> ℹ️ - Jira only allows to add approvals for JSM project workflows. It means that a Software or Business project will not benefit of this Post function feature.
> ℹ️ - Mindpro Sync reads the Jira Service Management's default "Approvers" field only. In case you create another field for that purpose or have another app that creates a different "Approvers" field, the system will not be able to read it and the approvers may not be correctly set.

---

### **Need any help?**

Didn’t find what you were looking for? Raise a ticket [here](https://mindpro.atlassian.net/servicedesk/customer/portal/3) or get in touch at [support@mindproapps.com](mailto:support@mindproapps.com)