| Access Pending |
The screen shown to someone who is signed in but has no active membership with a role. See Signing in. |
| Access request |
A request for a new organisation, submitted through the Get started form on the website. |
| Activity timeline |
The audited changes to one item, shown in task details and on release candidates. |
| Admin |
The organisation role that manages members, product structure, task requests, approval rules and releases. |
| App |
The top of the work hierarchy: a product surface your organisation builds and tests. |
| App access |
The list of apps a non-admin member can see. |
| Approval |
A sign-off a release candidate needs, such as QA Approved. Created automatically from approval rules. |
| Approval rule (approval requirement) |
An admin-defined rule saying which approval an entity type needs, optionally only for a work type, priority or release version. |
| Audit log |
The immutable record of privileged and workflow changes, readable by Admins. |
| Blocked |
An item with a blocked reason or an unfinished dependency. Also a QA result meaning testing couldn’t be completed. |
| Bulk import |
Creating apps, groups, modules, submodules and tasks from one JSON document. |
| Cascade |
Applying a workflow stage change on an app, module or submodule to all its children. |
| Client |
A stakeholder role that follows release progress and comments. |
| Comment |
A note on an app, module, submodule or task. Can mention people with @. |
| Dependency |
A link saying one item waits on another. |
| Developer |
The organisation role that delivers assigned tasks and triages issue reports. |
| Device defaults |
A tester’s saved platform, environment, device and OS, stored in their browser and used to pre-fill forms. |
| Evidence |
Screenshots, recordings and video links that support a QA result or task request. |
| Expected result |
What a task should do when it works, written by an admin. Testers judge pass or fail against it. |
| Feedback submission |
An issue report or a suggestion a tester sends against a task. It never changes the task’s stage. |
| Issue report |
A feedback submission saying the task didn’t behave as expected. |
| Member |
A person with access to an organisation, with a role and status in it. |
| Milestone |
A dated goal that items can be linked to. |
| Module |
A testable area of an app. |
| Notification |
An in-app message about something you’re responsible for or mentioned in. |
| Organisation |
One customer company, and QA Sync’s unit of tenancy. All product data belongs to one organisation. |
| Override |
Promoting a release that isn’t ready, with a written reason. Admins only. |
| Platform operator |
QA Sync staff who review access requests and provision organisations. Holds the Super Admin role. |
| Product Manager |
The organisation role that tracks portfolio, roadmap and releases and gives product approval. |
| Production |
The final delivery stage: shipped. Reached only by promotion. |
| Promotion |
Moving a Ready to Ship item to Production from the release board. Admins only. |
| QA run / QA result |
One round of testing on a staging task, ending Passed, Failed or Blocked. |
| Readiness |
A score and status (Not Ready, At Risk, Ready, Approved for Release) for a release candidate. |
| Release board |
The screen for reviewing release candidates, deciding approvals and promoting. |
| Release candidate |
An item in Ready to Ship (or already released) shown on the release board. |
| Release version |
A free-text version label on items, used to group release analytics. |
| Retest |
A new QA run on a task whose previous run failed or was blocked. |
| Role |
What a member can do in an organisation: Admin, Product Manager, Developer, Tester, UI Designer, Client or Viewer. |
| Row Level Security (RLS) |
Database rules that check every read and write against the caller’s organisation, role and access. |
| Sprint |
A dated delivery window that items can be linked to. |
| Stakeholder |
A UI Designer, Client or Viewer. |
| Staging |
The delivery stage in which a task is visible to testers. |
| Status history |
The record of an item’s workflow stage changes. |
| Submodule |
A smaller area inside a module. Every task belongs to one. |
| Suggestion |
An improvement idea a tester sends on a task. Developers can escalate it to admins. |
| Super Admin |
The platform operator role. Not an organisation role. |
| Task |
A unit of work with test instructions and an expected result, assigned to a developer and tester groups. |
| Task request |
A proposal for missing test coverage, reviewed by admins. |
| Tester |
The organisation role that runs QA on staging tasks and requests missing coverage. |
| Tester group |
A team of testers in one app. Tasks are routed to testers through groups. |
| UI Designer |
A stakeholder role that follows release readiness and comments. |
| Viewer |
A stakeholder role with a read-only progress view. |
| Workflow stage |
Where an item is in delivery: Draft, Backlog, Planned, In Progress, In Review, Staging, Ready to Ship, Production or Deprecated. |
