ClientJ user flows

These flows describe the intended experience. They are not instructions for an implemented interface; screen names and controls are still undecided.

Report an incident

1. Open the incident collection and start a new report.
2. Describe the sighting and provide the required incident details.
3. Submit the report and review the saved incident.

If Core rejects the report, the interface should explain the problem and preserve the entered information for correction.

Investigate an incident

1. Find an incident in the collection and open its details.
2. Review the report and its current progress.
3. Record an allowed update as the investigation proceeds.
4. Record the resolution when the incident is resolved.

Assignment controls and status choices depend on the rules established in Core.

Follow progress

A reporter should be able to return to an incident and understand its current state. The proposed Jira-inspired presentation emphasizes visible structure and detailed records. Search, filters, boards, and history should be documented only when their behavior is established.

Loading, an empty collection, a missing incident, and a failed request should each have clear feedback.