Admin guide

As an Admin you run your organisation’s QA Sync: who has access, how the product is structured, what gets tested, and what ships. You see every app in your organisation.

What you see

Your workspace is at /app/admin. The header has quick actions (Provision User, Add App, Add Group, Add Module, Create Task, Bulk Import) that change with the active tab, and a refresh control for the current tab.

Tab	Use it to…
Overview	Check delivery health, QA pressure, release readiness and people load at a glance.
Analytics	Dig into cycle time, stage aging, throughput, workload balance, bottlenecks and release confidence.
Hierarchy	Browse apps → modules → submodules → tasks as a tree, with status, progress and blockers. Filter by app, status, priority and blocker state.
Apps	Create, edit and delete apps.
Groups	Create, edit and delete tester groups.
Users	Add and manage members.
Modules & Submodules	Create, edit and delete modules and submodules.
Tasks	Manage tasks in seven sub-tabs (below).
QA	Review every QA run, with filters and evidence.
Audit History	Search and filter the audit log; clean up aged entries.

Tasks sub-tabs

Sub-tab	Shows
Kanban	Every task as a card in its workflow stage. Drag cards between columns. Filter by app, module, submodule, assignee, status, priority, milestone, sprint, release, environment, blocker and overdue state.
Planning	Tasks in Draft, Backlog or Planned.
Execution	Tasks In Progress or In Review. (Opens by default.)
Staging	Tasks in Staging, waiting for or under QA.
Release	The release board: release candidates, readiness, approvals, promotion and approval rules.
Feedback History	Tasks with feedback submissions, sortable by date, module or title.
Task Requests	Tester and developer requests waiting for review. The badge shows how many are pending.

A typical day

1. Glance at Overview for failed QA, blocked items, overdue work and pending requests.
2. Clear Tasks → Task Requests: publish, merge, review or reject.
3. Check Tasks → Staging and QA for failed or blocked runs that need a decision.
4. On Tasks → Release, complete admin approvals and promote ready items.
5. Adjust members and access as the team changes.

Common tasks

Set up the product structure

1. Apps → Add App: name, description, workflow stage.
2. Groups → Add Group: app, group name, description.
3. Modules & Submodules → Add Module: app, module name, description, platforms (Web, iOS, Android), environment, build/version, tester groups, workflow stage. Then add submodules inside the module.

Details in Apps, modules and sprints.

Create a task

1. Open Tasks and select Create Task.
2. Choose the Module and Submodule.
3. Enter the Task Title, Type (Functional, UI/UX, Performance, Security) and Description.
4. Write Test Instructions: the steps a tester should follow.
5. Write the Expected Result: what should happen if the feature works. Testers judge pass or fail against this.
6. Choose Assign Developer and Assign Tester Groups.
7. Optionally set a Build/Version Override, the Workflow Stage, and planning fields: priority, work type, risk level, estimated and actual hours, story points, complexity, start and due dates, milestone, sprint, release version, owner, reviewer, QA owner, and blocked reason.
8. Optionally add Dependencies on other items.
9. Save.

Tip

A clear expected result is the single most important field. Write it as an observable outcome: “The order confirmation page shows the order number and a success banner.”

Move a task between stages

• On the Kanban board, drag the card to another column. QA Sync blocks moves to Ready to Ship unless the task’s latest QA result is Passed, and blocks moves to Production, which happen only through promotion on the release board.
• In the task editor, change Workflow Stage.

If a task has unresolved dependencies, QA Sync asks you to confirm before moving it. See Task lifecycle.

Change status on an app, module or submodule

Edit the item and change Workflow Stage. If it has children, QA Sync asks whether to apply the stage to them too. Choose apply to cascade it down, or skip to save only this item; the parent then keeps its rolled-up status until its children move.

Review a task request

1. Open Tasks → Task Requests and select View Details on a request.
2. Read the tester’s context and open any attachments.
3. Select Review Request (or Continue Review if it was reviewed before). Under Review Action, choose Mark as Reviewed, Publish as New Task, Merge with Existing or Reject Suggestion.
4. Correct the module, submodule or title if needed, add an Admin Note (Optional), and when publishing choose tester groups and an optional developer.
5. Select Save & Apply Action.

Details in Task requests.

Review QA results

Open the QA tab. Filter by app, module, submodule, tester, QA status, severity, environment and retest state. Open a run to read expected and actual results, tester notes, reproduction steps and evidence.

Approve and promote a release

1. Open Tasks → Release.
2. Select a release candidate. Review its readiness score, missing approvals, failed QA, blockers and overdue items.
3. In the approval checklist, select Approve, or enter a reason and select Reject.
4. When the candidate is Ready, select Promote To Production and confirm.
5. If it isn’t ready but must ship, write an override reason and select Promote With Override.

Details in Approvals and releases.

Bulk import a test plan

Select Bulk Import, paste or upload a JSON document describing apps, groups, modules, submodules and tasks, validate it, then import. See Bulk import.

Delete things safely

• You can’t delete a task that already has feedback submissions; move it to Deprecated instead.
• Deleting an app, module or submodule asks for confirmation. Prefer Deprecated to keep history.
• Members: prefer Revoke access over Delete permanently.

Tips

• Keep at least two Admins.
• Use tester groups to route work; a task with no groups never reaches a tester.
• Use the Hierarchy tab with Blocked only to find what’s holding up a release.
• Open a task’s details to see its activity timeline, status history, dependency summary, tester submissions, attachments and comments in one place.

What you can’t do

• Grant the Super Admin role. It is reserved for QA Sync platform operators.
• Rename your organisation or change its tenancy. Contact QA Sync.
• See other organisations’ data.
• Reset a member’s password from the app. Contact QA Sync if someone is locked out.