Skip to main content
This plan covers recent travel and venue work on the gig. Some of it is API only, with no screen yet. Those parts are listed under API only so testers do not look for them. Read the QA testing guide before you start.

At a glance

None of these features has a feature flag. What’s ready shows where each area is deployed and whether TestFlight has it. An area that is only on dev needs a development or Revyl build.

Before you start

  • A gig with a venue that has a full street address. Uber and Lyft need an address the app can find on a map.
  • A ride on the gig with a pickup and drop-off address, and your crew account as a rider. Managers add rides on web, in the gig’s travel section. Choose the rideshare kind for the Get a ride checks.
  • Key spots on the venue. On web, open Venues → the venue → Key spots, add a spot with a name and kind, tap Drop pin, and click the map. Add at least two.
  • Two accounts: a crew member and an owner or admin.

In scope

Ride card (mobile)

Traveler details (mobile)

Venue panel, Directions, and sharing (mobile)

Venue map (mobile)

Crew notes on key spots (mobile and web)

A crew note belongs to the venue’s key spot, not to one gig. It shows on every gig at that venue and on the venue page.

Changes list (mobile)

The Changes section shows on the gig for everyone except org owners and admins, who see Recent activity instead. Test it as crew or a coordinator.

API only: agents test these

These checks go straight to the API. Crew flights, rides, boarding passes, and reading a confirmation have no screen yet, so testers skip them. Key spot notes have screens now (TV-45 to TV-53), and TV-39 checks the same rules at the API. Agents run these with npm run api against a local stack. See the agent runbook.

Out of scope

Do not file these as bugs. They are not built yet.
  • Adding or uploading your own flights and rides in the mobile app (ENG-2294).
  • A My travel screen on mobile (ENG-2295) and crew travel editing on web (ENG-2296).
  • A mobile screen that reads a travel confirmation (ENG-2323). The API is in TV-54.
  • Seeing boarding passes or confirmations on any screen.
  • Editing key spot pins on mobile.

Known limitations

  • Uber and Lyft need an address the app can find on a map. The seeded demo venue has none, so Uber and Lyft are correctly missing there.
  • On Android, the app looks up an address only when location access is already on. It never asks for location for this.
  • The fallback alert that shows when another sheet is open labels the copy button Copy Address.
  • “New” in Changes needs a previous visit on the same device. On a first visit, nothing is new.
  • The map loads its code from the internet. Offline, it always falls back to the list.

Needs a real device

For agents

  • Personas for npm run api on a local stack: owner.busy, admin.busy, coord.busy, and crew member.multi or member.invites.
  • Path parameters are snake case on travel routes (event_id, flight_id, ride_id, booking_kind, booking_id) and camel case on venue spot routes (eventId, spotId).
  • The signed upload for TV-38 is a separate curl -X PUT with the headers the create call returns. npm run api sends JSON only.
  • Hybrid check for the ride card: create a ride as member.multi with service UBER and a drop-off, then run TV-01 to TV-05 on a simulator as that member.
  • Existing tests: e2e/tests/transports/my-flights-and-rides.test.ts and booking-documents.test.ts.
  • Analytics (PostHog, mobile key spot notes): venue_spot_note_added, venue_spot_file_added, venue_spot_note_add_failed, venue_spot_note_updated, and venue_spot_note_deleted. They carry no note text, file names, or spot names.