Hide urgency and impact fields on security incident in SIR workspace? Will it have any impact?

[ApurvaB2101]

Hi,

We have a requirement to hide impact and urgency fields present in security incident in SIR workspace. If we hide it, will it have any impact on the flow?

[Mark Manders]

Why? What are you trying to gain by hiding them?

Impact and Urgency calculate priority, so hiding them would disable the possibility to change the priority. And even on Security Incidents, the priority can change. 

[ApurvaB2101]

Hi ,

In SIR, Priority value does not change based on Impact and urgency. Priority is an independent field

[Community Alums]

If you hide the Impact and Urgency fields from the security incident form in SIR workspace, it won’t directly stop your flows or scripts from running. The system will still have those field values behind the scenes, and any automated business rules or data policies that use them will still work. So technically, just hiding the fields on the UI doesn’t break the process immediately.

However, in most setups, Impact and Urgency together are what determine the Priority of an incident. If users can’t see or change these fields, they won’t be able to correct or adjust Priority when needed. This could indirectly affect escalations, SLAs, or other automated workflows that depend on having the right Priority value. To be safe, it’s a good idea to check if you have automation that sets these values correctly, and test your flows after hiding the fields to make sure nothing important is missed

[ApurvaB2101]

Hi,

In SIR, Priority value does not change based on Impact and urgency. Priority is an independent field