--- title: "Setting Custom Approvers via Post function" canonical: "https://helpcenter.mindproapps.com/space/sync/2003402761/Setting%20Custom%20Approvers%20via%20Post%20function" format: markdown --- > ℹ️ **Summary: **Learn how to set custom approvers in your workflow using our dedicated post-functions. ### **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 two dedicated post-functions that can be added to your JSM workflow to set approvers during a status transition. > ℹ️ **Good to know:** > ℹ️ > ℹ️ Post-functions are only available in Jira for workflows associated with "company-managed” space types. The "team-managed” space have different rules to perform actions. Click [here](https://support.atlassian.com/jira-software-cloud/docs/available-workflow-rules-in-team-managed-projects/) to learn more. --- ### **1 - How to add the Mindpro Sync Post function for assigning approvers based on the workflow transition** Use this post-function to add approvers based on a workflow transition. In this case, whenever the user performs the transition in the workflow that contains this post-function, the system will assign the defined approver(s) to the “approvers” field. To configure this post-function, please follow the steps below: - Navigate to Jira Settings -> Work Items -> Workflows - Select the workflow you'd like to use and click "Edit” - Click on the transition upon which the IdP data should be updated. - Find the "Rules" option in the right panel, and click on the "Add Rule" icon ![Mindpro-1759792791442-2x.png](media://745c37e2-259a-4a27-8e40-4377c60ab99f) - From the “Add Rule” window, select the"**Mindpro Sync: Assign Issue Approvers**" option: ![Mindpro-1759794132296-2x.png](media://6cb77896-629b-41dd-8ad3-9ccb2a614ce0) - From the next page, select the "Approvers" field and choose the Jira users to be the "Issue Approvers" (You can add more than one approver if required ). Then, click on “Add": ![Mindpro-1759794440103-2x.png](media://37274393-e889-4b05-812f-9a6bc6293eb9) - The new post-function added will appear in the panel. Click on the "Update Workflow" button on the top of the screen to save the changes. ![Mindpro-1759794656954-2x.png](media://802a86cd-92f6-4910-a055-06d26ef2307f) > ℹ️ **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(s) as the issue approver(s). No additional configuration is needed. --- ### **2 - How to add the Mindpro Sync Post function for assigning approvers based on the content of a specific dropdown field.** Sometimes the same process demands different approvers depending on certain criteria. This post-function allows to set approvers dynamically during a workflow transition, based on the content of a dropdown field. In this case, whenever the user performs the transition in the workflow that contains this post-function, the system will look at a specific dropdown field, check its content and, based on this, will set specific approver(s) to the “approvers” field. For example, you can select different approvers depending on the ticket severity or depending on the content of a system or custom field. To configure this post-function, please follow the steps below: - Navigate to Jira Settings -> Work Items -> Workflows - Select the workflow you'd like to use and click "Edit” - Click on the transition upon which the IdP data should be updated. - Find the "Rules" option in the right panel, and click on the "Add Rule" icon ![Mindpro-1759792791442-2x.png](media://745c37e2-259a-4a27-8e40-4377c60ab99f) - From the “Add Rule” window, select the "**Mindpro Sync: Assign Approvers Dynamically**" option: ![Mindpro-1759794958117-2x.png](media://b00469f2-5a3c-4842-bbf0-869dfeaf19b8) - From the next page, select the dropdown field in which content will be considered and choose the Jira users to be the "Issue Approvers" based on each content criteria. (You can add more than one approver if required ). Then, click on “Add": ![Mindpro-1759795123541-2x.png](media://d06db94d-8521-46b1-8b04-d36e7e24f17f) - The new post-function added will appear in the panel. Click on the "Update Workflow" button on the top of the screen to save the changes. ![Mindpro-1759795348352-2x.png](media://f6bf66ac-f2c0-4b91-b9ce-399e65ce5761) > ℹ️ **Good to know** > ℹ️ > ℹ️ Currently, this post-function only supports system or custom fields that are “**dropdown**" types. Future releases may allow other field types for selection. --- ### **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://helpcenter.mindproapps.com/space/sync/1992458261/Configuring+the+approver+auto-assign)) or the options 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/sync/pages/1992458261/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 space 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)