Incident Task's Priority calculation based on Impact and Urgency
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Forum,
We have noticed that Incident Task's priority is not changing when we change the impact and urgency. We even verified the same in OTB (PDI) instance as well. Is it an expected behavior? . If we need to change priority on basis of Impact & urgency (probably as per the configuration in Priority Data Look up rules), what is the better way to handle without customization?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
22 hours ago
Hi @madhuv ,
this is the expected behavior for Incident Tasks. Unlike parent Incidents, Incident Tasks don’t automatically inherit priority calculation from Impact/Urgency.
Priority Data Lookup Rules are usually set up for the Incident table only.
To get around this, you can create a Business Rule on the Incident Task table. This rule will trigger whenever Impact or Urgency changes, and then it will calculate the priority using the same logic as incidents.