How to read the status columns
- Dev, QA, Production: whether the code has reached that environment. Web on QA is
qa.app.soundchecklive.io. Production web isapp.soundchecklive.io. No mobile build talks to the QA backend, so a mobile-only row shows n/a under QA. - TestFlight: whether a tester with the latest TestFlight build can test it. TestFlight carries the mobile code from the
qabranch but calls the production API. A feature that needs a new API change works in TestFlight only after that change reaches production. - Tickets: the Linear tickets for the feature. Their merged PRs decide the status.
dev was promoted to qa (PR 5169) and qa to main (PR 5140). Agents refresh a row by checking each ticket’s PRs with the commands in the agent runbook.
Ready for QA
Blocked means the code is deployed but a setup step is missing. Clock-out reminders and alerts need the scheduled job from ENG-2037 in each environment.
Agents only
These features are API only. They have no screen yet, so human testers skip them. Agents test them with the steps in each plan’s API only section.Not in scope this cycle
Do not test or file bugs for these. Each test plan’s Out of scope section has the full list for its area.- Crew adding flights, rides, or uploads in the mobile app, and a My travel screen (ENG-2294, ENG-2295).
- A mobile screen that reads a travel confirmation (ENG-2323).
- Text invite links opening the app on production (PR 4047, held).
- Picture messages to text-only chat crew. The
event-chat-mmsflag is off. - Fold and unfold on foldable iPhones (ENG-2053, ENG-2054).
- Android tablet layouts (ENG-2056).
- Overtime and hourly invitations in the time clock.
- Mobile admin settings that match web. Org settings stay on web.