Auto Populate Assigned To upon resolving

[menardJA]

I got a request to have the Assigned To field either auto populate or become required when resolving an incident. I tried just using a UI policy  to make it required when status is resolved but it seems to auto delete when I save the Policy using form builder.

I also tried to configure a business rule to make the Assigned To field populate with the last updated user when an Incident is resolved but I cannot seem to grab that information when using current.updated_by on my business rule

[Natan F Rosa]

Hi @menardJA 

To make it easier to understand, do you have any images or examples of what you did and what is happening?

[menardJA]

Hi @Natan F Rosa 

I attempted to put a business rule like seen in the screenshot here that when the Incident State is set to Resolved it sets assigned to based on the current user who updated the incident. However when I hit save it is deleting the value I am providing

[Viraj Hudlikar]

Hello@menardJA 

Instead of creating ui policy from form builder give try with normal way it will work. Also, try to share some screenshots if possible so we can have a look and guide you.

Also writting br which updates assigned to with last updated person is not good idea. You can try for on change cleint script for state field and when it changes to resolve state you can make assigned to mandatory so whoever does this change now he has to fill in assigned to field before saving.

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

Thanks & Regards
Viraj Hudlikar.

[Juhi Poddar · Accepted solution]

Hello @menardJA 

You can make the Assigned To field mandatory when the State is set to Resolved by creating a UI Policy—no coding required.

Refer to the screenshot below for the necessary configuration setup to achieve this.

UI policy configuration setup:

Ui action:

Result:

Hope this helps!

"If you found my answer helpful, please like and mark it as an "accepted solution". It helps future readers to locate the solution easily and supports the community!"

Thank You
Juhi Poddar