After upgrade to Jakarta, customers are facing issue with the automatic change of the priority field based on Impact and Urgency change.
Steps to Reproduce
- Spin a developer instance in any version prior to Jakarta
- Upgrade to Jakarta
- Access the instance, open an incident, and try changing the Impact and Urgency choice list values
The Priority Lookup does not seem to get triggered immediately after upgrade
- Clearing the instance cache
- Clearing browser cache
This can be avoided by setting the property glide.ui.batch_glide_ajax.enabled to false, which disables all batching of GlideAjax requests on the instance.
Related Problem: PRB1102205