# Required Fields on Resolve

Customize incident resolution forms to capture critical incident data, ensure consistency, and streamline post-incident analysis.

The Required Fields on Resolve feature allows you to tailor the incident resolution experience to your team's needs. By configuring which fields appear, adding custom options, and setting required fields, you can ensure every incident captures the most relevant and structured information. This streamlines the resolution process and guarantees consistent data collection for post-incident analysis and reporting.

The Required Fields on Resolve feature includes:

- Customized fields in the order you specify on the [Incident Resolution Form](#configure-an-incident-resolution-form)
- Clearly marked required fields (**Enterprise for Incident Management plan only**)
- Optional fields for additional context
- The standard resolution notes field

> **Required User Permissions:** Global Admins and Account Owners can configure Incident Resolution Forms.

> **Supported Interfaces:** Required fields on resolution are supported in the web app, Slack, and mobile app only. They are not supported in the following cases, where the Incident Resolution Form does not appear and incidents resolve without required details being captured:
>
>   - Resolving incidents via SMS or voice notifications.
>   - Manually resolving an incident's alerts from the Alerts section of the incident's details page. This resolves the underlying incident automatically, and you will not be prompted for required fields or a resolution note.

## Configure an Incident Resolution Form

> **Prerequisites:** You must first [configure Incident Types](/incident-management/incidents/incident-types#configure-incident-types) with [Custom Fields](/incident-management/incidents/custom-fields-on-incidents#configure-custom-fields) before configuring an Incident Resolution Form.

1. Navigate to **Incidents**  →  **Incident Types**.
2. Select the **Forms** tab.
3. Click **Add Field** to add fields to the resolve form.
4. Select the field(s) you want to add. Available fields include:
   - Fields specific to your incident type (for example, Root Cause, Customer Impact)
   - Inherited fields from base types (for example, Environment URL)
   - System fields (for example, Priority)
5. _(Optional, Enterprise for Incident Management plans only)_ Select the **Required** checkbox to make the field(s) required to resolve the incident.
6. Click **Add Fields** to confirm your selection.

## Edit Field Order

You can edit the order in which fields appear on your Incident Resolution Form.

1. Navigate to **Incidents**  →  **Incident Types**.
2. Select the **Forms** tab.
3. Click  to the right of the field you want to move.
4. Select **Move Up** or **Move Down** to arrange fields in your preferred order.

> **Tip:** Position the most important fields at the top of the form.

## Test Incident Resolution Form User Experience

To preview the form:

1. Navigate to an open incident.
2. Click **Resolve** to preview how the form appears to end users.
3. Verify that required fields are properly marked and that the field order meets your needs.

> **Notes:** - Field visibility and requirements are configured in the PagerDuty web app. Keep those definitions up to date to ensure consistent behavior on mobile.
>   - The mobile experience mirrors the web app configuration.
>   - Any field marked with a red asterisk is required before an incident can be resolved.

<br />