Is there a way to enforce that a custom field is populated when resolving an incident? Our current use case is to create a custom field for Categorization of the resolution. However we don’t see anyway of enforcing that it gets updated. Without enforcement then we are just running audit reports and chasing people down. Not the best use of time. If there was a way to enforce that the field gets updated, that would remove this concern.
Hi
PagerDuty currently allows you to add and edit custom fields on incidents, which is great for categorization and other metadata needs. However, as of now, there is no built-in feature to enforce that a custom field is populated before an incident can be resolved.
The main workaround is as you state, to run audit reports and follow up with responders who missed required fields, which I understand isn’t ideal. I believe you can also try enforcing these as part of your itsm workflow and then sync back to PagerDuty. There should be other community members that can help brainstorm such a solution in this topic.
If this is a critical need for your workflow, I’d recommend submitting feedback to PagerDuty support or your account manager, as this is a feature many users would benefit from. I’ll also try and check internally if there’s any traction for such a feature or improvement.
Thank you and have a nice day!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
