Feedback and suggestions

A feedback submission is a tester’s report against a task. It’s either:

• an issue report: the task did not behave as expected, with issue title, type, severity, actual result, steps to reproduce and device details; or
• a suggestion: the task works, but something could be better.

Developers triage issue reports on their tasks and can escalate suggestions to admins. Admins see all feedback in one place.

Feedback submissions and QA runs

Testers record results on staging tasks as QA runs, which drive the task lifecycle. Feedback submissions are a separate record with their own triage status, used by the developer Review Queue and QA Returns tabs and the admin Feedback History. Sending one never moves the task: only a failed QA run returns it to development.

Send an issue report or suggestion

Testers send feedback on any task in their queue:

1. In Queue, select Report issue / Suggest on the task, or select Report issue / Suggest improvement inside a QA run.
2. Choose Report an issue or Suggest an improvement.
3. For an issue, fill in the summary, what went wrong, type, severity, actual result and steps to reproduce, and attach a screenshot if it helps. For a suggestion, describe the improvement.
4. Select Preview, then Submit.

Feedback opened from a QA run returns you to that run, so you can still record its result.

What an issue report contains

Field	Notes
Issue title, issue type
Severity	Low, Medium, High, Critical
Expected result	From the task, written by an admin.
Actual result, steps to reproduce
Device, device model, OS version
Screenshot	One image, stored privately.
Reported by, app › module › submodule, app version

The issue triage flow

Issue reports have their own status, separate from the task’s workflow stage:

New → Triaged → In Progress → Fixed → Needs Retest → Closed
                     ▲                      │
                     └──────────────────────┘

Status	Meaning
New	Just reported.
Triaged	A developer has looked at it.
In Progress	Being fixed.
Fixed	Fix is done.
Needs Retest	Ready for a tester to confirm. From here it goes back to In Progress or to Closed.
Closed	Done.
Won’t Fix	Closed without a fix.

Closed and Won’t Fix are complete statuses; complete reports move to the developer’s History tab.

Triage an issue (developers)

1. Open Review Queue (New and Triaged reports) or QA Returns (In Progress, Fixed and Needs Retest).
2. Filter by search, app, status, module, submodule or severity.
3. Open a report to read it in full.
4. Move it to the next status.
5. Select Add Note to record internal notes. Notes are visible to developers and admins, not to testers. You can edit or clear a note later.

Developers can only update status and notes. They can’t reassign a report or its task; admins own assignment.

Every status and note change is written to the Audit log.

Suggestions

When a tester sends a suggestion, it appears at the top of the developer’s Review Queue, separate from issue reports.

Escalate a suggestion (developers)

1. Select the suggestion to open it.
2. Under Admin Review, select Request Admin Review.

QA Sync creates a task request titled Review improvement for followed by the task name, with the suggestion as its description. Each suggestion can be escalated once; afterwards the card shows Submitted.

Feedback History (admins)

Tasks → Feedback History lists every task that has feedback, with assigned groups, build, developer, number of reports and latest submission. Sort by date, module or title, and select View Details to open the task with its submissions and attachments.

A task that has feedback can’t be deleted; move it to Deprecated instead.