Incident Task's Priority calculation based on Impact and Urgency

[madhuv]

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? 

[Ankur Bawiskar]

@madhuv 

impact and urgency logic is OOTB handled for incident table and not for incident_task table.

You can configure data lookup rules for incident_task table similar to how it's configured for incident table

No customization required in this case then

Define priority lookup rules 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@madhuv 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Bhuvan]

@madhuv 

Incident task table 'Priority' is not calculated based on impact and urgency.

If you want to replicate the functionality same as incident table, make Priority field read-only and make impact & urgency as mandatory and create data lookup rules. Follow below article for reference,

https://www.servicenow.com/community/servicenow-ai-platform-forum/how-to-set-priority-based-on-impac...

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[Bhuvan]

@madhuv 

Did you get a chance to review this ?

As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan