assigned to field not becoming mandatory

suresh kaliappa · 3 weeks ago

Hi all,

I created 1 custom client script to make assigned to field mandatory in dev instance. In dev instance it is working fine but i migrated the same code to QA without any changes. But same code not working in QA instance. The assigned to field not becoming mandatory. so can someone please suggest what might be the issue?

Ankur Bawiskar · 3 weeks ago

@suresh kaliappa

any other UI policy is making it non-mandatory in QA?

what debugging did you do?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

View solution in original post

Abhishek_W · 3 weeks ago

Hi @suresh kaliappa ,

Most probably UI policy and client script is conflicting because of which it is unable to make that field mandatory. Also properly check update set contains that changes or not .

If this helps you then mark it as helpful and accept as solution.

Regards,

Abhishek