You want the responder to leave a note when they acknowledge an incident, or confirm the blast radius before closing it. Until now there was nowhere in Flashduty to collect that, so teams fell back on chat threads or a separate ticketing system.
Custom incident forms now let you configure a separate form for each of three actions: create incident, acknowledge incident, and resolve incident. A form can include custom fields, a free-text note, and image uploads, and each element can be set to required or optional, and shown only when a condition is met, for example requiring the impact scope field only when severity is high.
Written atomically with the state change
Submitting an acknowledge or resolve form and updating the incident state happen as a single atomic write. You will not see a form get submitted while the state change fails to apply, or the state change go through while the submitted content is lost.
One interface across five IM platforms
Tapping acknowledge or resolve in DingTalk, Feishu, Slack, Microsoft Teams, or WeCom opens the same Console H5 form drawer. There is no separate form implementation per platform, so the experience is identical regardless of which IM the responder is using.
Configuration and list pages rebuilt
The field configuration and form management pages were redesigned. Drag to reorder fields, and click any row to edit its display condition, required rule, and help text.
Mobile fix included
In the mobile app, acknowledging or resolving an incident with no form configured no longer redirects to an empty form page first. It completes the action directly.
Getting started
Go to the incident configuration section of the Flashduty console and open Custom Forms.
See the product documentation for details.
