Configurable custom field forms

Custom fields are an incredibly important part of our product - they allow incidents to be categorised and tracked in a way that suits your organisation.

That said, long lists of custom fields can become unwieldy: in the dashboard (and in Slack) your form can become long. In the past, we introduced a change to hide “Automatically set” custom fields below the fold in the dashboard version. We also allow the configuration of custom fields to only show for specific incident types. These changes solved some of the problem, but not all of it.

We already allowed form configuration for other incident forms (Declare, Update, Resolve, etc), and have now extended this to support the custom fields form:

You can now opt-in to a new configurable custom fields form that will allow you to re-order, conditionally show, or completely hide fields from the form. There will be no change to your forms if you don’t choose to opt in.

If you opt-in:

• You can have one custom field form per incident type
• We will set up a form for you with all your fields on it, ordered by their rank
• These fields can then be re-ordered, conditionally shown, or completely hidden from the form
• Fields on the form cannot be made required, as we don’t want to prevent people setting other fields
• New custom fields won’t be added to the configurable forms by default

Retrospective incidents for Microsoft Teams

You can now declare an incident after it has happened in Microsoft Teams with retrospective incidents. This can be done in the dashboard, and you can choose whether or not we announce it, which means you don’t have to worry folks unnecessarily.

Skip channel creation based on incident mode

You can now add a condition on incident Mode under the “Skip channel creation” section of your incident type settings. As an example, this can be used to ensure that retrospective incidents don’t get an associated channel when you create them.

🚀 What else we’ve shipped