Value Proposition Statement

Easily resolve incidents while learning how to use Camunda

User Problem

Inconsistent UX: Play's incident management UX is different from Operate, making it harder to learn the product
Irrelevant Guidance: The hard-coded guidance to set variables is only relevant for some incident types.
Conceptual Education: There are few opportunities in-product to teach users about how the product works, but this is important for developers who are responsible for maintaining the system.

Let AI teach you how to prevent and fix the incidents you run into while playing your process.

UX Alignment: OUT OF SCOPE

~(M) When I have an incident in Play, I want an expanded banner that shows the incident so I can quickly fix it~
~(M) When I have an incident in Play, I want only actionable information so I can stay focused on my task~
~(S) When I interact with the incident action icon, I want to be drawn to the next step in the flow so I can resolve my incident~
~(M) When I'm viewing an incident in Play, I want a clear call to action so I know how to fix it~

Generative Guidance:

[ ] (M) When I'm viewing an incident in Play, I want to get AI-generated advice on...
- its meaning so I understand Camunda
- its root cause so I can fix my diagram
- how to resolve it so I can keep the diagram flowing
[ ] (M) As a user without access to AI features, I want easy guidance on how to enable them so I can easily fix my incidents

Filters, Job Id, and Creation Date are irrelevant
The incident drawer should be expanded by default
The primary action could focus the user on the incident or on the Operations section
The secondary action could go directly to open the Kapa dialog
In the incident drawer, there should be an eye-catching CTA to learn how to fix the issue
- If AI is used, an AI-related symbol would be helpful
The prompt could be:
- I reached a {connectorType, else BPMNElementType} and got this incident. What does it mean, what is the root cause, and how do I fix it?
  Incident type: {incidentType}
  Error type: {errorType}
A Statsig experiment will help us establish the lift

^{:robot: This issue is automatically synced from: source}