In our org we have some request types with approvals. When a user raises any ticket, we should add the approver group manually every time. So require any solution to automate the approval group add default.
Hi @Marc -Devoteam- ,Thanks for the reply. Here the user who rise ticket doesn't know which approver group to be added to, so we want to do by automation. Tried this solution, and it's not working .
Automation
From your service project, select Project Settings> Automation.
Select Create a Rule in the top-right corner.
Select a trigger for the rule. In this case, you can select the Work item created trigger
Configure the trigger settings (if the trigger is different than Work item Created) and select Save.
Select New component and add a New condition - Work item Fields condition.
Add the condition for the Request Type field to be equal to the required request type in your project.
Select New component and add a New action - Edit Work item.
In the Fields to Set section, add the Approvers field.
Add the default approvers from the dropdown panel.
Select Save.
You can also add the other request types by adding more conditions in this automation rule.
Give your rule a name, then select Turn it on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On my suggest the user doesn't have to choose, please read.
On a request type, add the approvers field, set the approvers field to hidden. On doing this action the field is required to have a default value set.
Set this value to the group where the members are who need to approve such a request.
If you use a Company managed project template, you can see this option on a field "Use a preset value and hide from portal"
Or are you using a Team managed project template, then you only option is automation, based on your automation, you need to add a Re=fetch work item action after setting to Component, otherwise the condition based on the component isn't in awareness of the issue yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I checked the settings you provided. It seems to be working for some request types, but for others, it is still prompting us to manually add the approver group.
Could you please take a look and let me know what might be causing this inconsistency?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marc -Devoteam- ,I tested this in my org using the same process across the required request types. after creating tickets, I noticed that some are automatically picking up the default approver groups, whereas others are still prompting for manual updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.