Request status reference
Review statuses, priorities, and categories for reported bugs, features, and improvements.
Requests shows product feedback and progress for your organization. This screen is read-only. The list updates in real time when progress changes.
Business value
Request status gives organizations one view of product feedback progress. Operators can focus on customer impact and evidence instead of repeated status questions. Separate status, priority, and category prevent confusion between urgent failures and long-term improvements.
| Operating goal | Request status role | Measure |
|---|---|---|
| Share progress | Provide a read-only current status for each request. | Status questions and old Triage requests |
| Collect impact evidence | Show priority and recurrence together. | Recurrences and affected operating journeys |
| Reduce duplicates | Add evidence to an existing request title. | Duplicate requests and requests with new evidence |
Examples
Example: A reservation save failure. Several branches reproduce the same condition. Each branch sends the event time, expected result, and reproduction steps for the existing request. The operator can compare recurrence and customer impact.
Example: A new statistics view. The request does not block current work. The administrator describes the decision, required measures, and expected frequency. The status still shows the review stage when priority is low.
Statuses
| Status | Meaning |
|---|---|
| Triage | The team is assessing impact and ownership. |
| Backlog | Review is complete, and the request awaits scheduling. |
| Unstarted | The work is defined but has not started. |
| Started | The assigned team is working on the request. |
| Completed | The defined work is complete. |
| Canceled | The work will not continue in its current scope. |
Completed does not always mean that every suggested idea was built. Review the request title, description, and latest status together.
Priorities
| Priority | Meaning |
|---|---|
| No priority | The team has not set a comparative priority. |
| Urgent | A severe impact needs immediate review. |
| High | Many customers or a critical journey have major impact. |
| Medium | A clear impact will follow planned scheduling. |
| Low | Limited impact places the request behind other work. |
Request volume does not determine priority by itself. The team also reviews customer impact, recovery options, frequency, and current plans.
Categories
A request can show Bug, Recurrence, Feature, Improvement, or Plan categories. Several categories can appear on one request. Categories support search and grouping. They do not replace status or a delivery commitment.
New requests and added information
For a new request, prepare the event time, organization, expected result, actual result, and reproduction steps. Remove customer personal data and secrets. Attach only the required screen area.
For more evidence, send the same request title through your customer support channel. Do not create a duplicate request. When the list differs from guidance, send the guidance time and screen to support. You cannot edit a request title or status on this screen.