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


  1. Spin a developer instance in any version prior to Jakarta
  2. Upgrade to Jakarta
  3. 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
Workarounds Provided:
  1. Clearing the instance cache
  2. 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

Seen In

There is no data to report.

Fixed In

Jakarta Patch 3
Jakarta Patch 4

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:36:11