Task requests
A task request proposes test coverage that doesn’t exist yet. It’s how a tester says “nobody has written a task for this”, and how a developer asks admins to act on a tester’s suggestion. Admins decide what happens to each request.
Where requests come from
Section titled “Where requests come from”| Source | How |
|---|---|
| Tester | Suggest New Task in the tester Queue. |
| Developer | Request Admin Review on a tester suggestion in the Review Queue. QA Sync fills in the request from the suggestion. |
Submit a request (testers)
Section titled “Submit a request (testers)”- In Queue, select Suggest New Task.
- A. Context / Device Information: Platform, Environment, Device Name, Device Model, OS / Version.
- B. Test Structure: Module, Submodule and Suggested Task Name. QA Sync lists similar existing tasks as you type. If one already covers your scenario, test that instead.
- C. Feedback Details: Reason this task is missing, Severity (Low, Medium, High, Critical), Feedback / Description, Expected Result, Actual Result, Steps to Reproduce.
- D. Attachments: optional screenshot (up to 6 MB) and screen recording (up to 25 MB).
- Select Save Draft, or Preview and then Submit for Admin Review.
Attachments are stored privately and shown only to admins and to the person who made the request.
Request statuses
Section titled “Request statuses”| Status | Meaning |
|---|---|
| Draft | Saved by the requester, not submitted. |
| Pending | Submitted, waiting for admin review. |
| Reviewed | Seen by an admin, not finalised. |
| Published | Converted into a new task or linked to an existing one. |
| Rejected | Closed without becoming a task. |
Draft, Pending and Reviewed count as open.
Review a request (admins)
Section titled “Review a request (admins)”- Open Tasks → Task Requests. Filter by status if needed. The tab badge shows pending requests.
- Select View Details. Read the full submission and open attachments.
- Select Review Request (or Continue Review, Review Again or Update Review, depending on the current status).
- Under Review Action, choose one:
| Action | Result | You must provide |
|---|---|---|
| Mark as Reviewed | Status becomes Reviewed. Nothing else changes. | — |
| Publish as New Task | Creates a new task from the request and links it. Status becomes Published. | Module, submodule, title and at least one tester group. Developer is optional (Leave unassigned for now). |
| Merge with Existing | Links the request to an existing task. Status becomes Published. | The task to merge into. |
| Reject Suggestion | Status becomes Rejected. | — |
- Optionally correct the module, submodule or suggested title and add an Admin Note (Optional). The requester sees the note.
- Select Save & Apply Action.
A published task is built from the request: its description and instructions include the coverage summary, why the coverage is needed, the suggested path to test, the observed result and the device context, and its expected result comes from the request. Review and edit it before moving it into delivery.
Every review outcome is written to the Audit log.
Delete a request
Section titled “Delete a request”Admins can delete a request from the Task Requests list with the Delete action. Prefer Reject Suggestion so the requester sees the outcome.
Track your requests
Section titled “Track your requests”Testers see every request they’ve made, with its status and admin note, under My Requests. See the Tester guide.