Skip to content

[Due for payment 2026-11-05] [$250] [Approve Travel R1] Trips table in Spend #104405

Open

Description

@stitesExpensify

Part of the Approve Travel in New Expensify project

Main issue: #659261
Doc section: Design doc, Detailed Implementation → Release 1, step 3
Project: https://github.com/orgs/Expensify/projects/354

Blocked by: #693360

Feature Description

Both trip column configs are empty today, and a trip search falls through to the expense view.

  • Add TYPE_CUSTOM_COLUMNS.TRIP and TYPE_DEFAULT_COLUMNS.TRIP: startDate, endDate, status, tripName, traveler, total.
  • View. Add a trip view before the expense view fallthrough, with its own renderItem, like the expense report view.
  • Row. Add a trip row, wide and narrow, built like the expense report row: start date, end date, a StatusBadge, trip name, the traveler's avatar and name, and the total in the trip's currency.
  • Header. Add trip headers for the columns above.
  • Action. The row action is View. View and tapping the row both open the trip room (#104412 moves this into the Spend wide panel).
  • No Approver column yet. It's added in #104417.

Everything user-facing here is behind the TRAVEL_APPROVAL beta (Release 1, step 0).

Manual Test Steps

  1. Sign in as a user with the beta who has several Expensify Travel trips.
  2. Open Spend → Travel → Trips.
  3. Verify each row shows start date, end date, status badge, trip name, traveler avatar and name, and total.
  4. Resize to a narrow layout (or use mobile) and verify the narrow row shows the same data.
  5. Tap View and verify the trip room opens. Go back, tap the row itself, and verify the same.

Automated Tests

  • Trip rows render the right columns, badge and View action.
Issue OwnerCurrent Issue Owner: @suneox

Activity

  1. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

  2. allgandalf commented on Oct 20, 2026

    @allgandalf
    Contributor

    trip search needs shouldReturnTripRooms: true in the jsonQuery, without it type:trip stays the expense search

  3. changed the title [-][Approve Travel R1] Trips table in Spend[/-] [+][$250] [Approve Travel R1] Trips table in Spend[/+] on Oct 28, 2026
  4. melvin-bot commented on Oct 28, 2026

    @melvin-bot

    ⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

  5. jponikarchuk commented on Oct 29, 2026

    @jponikarchuk

    Deploy Blocker #105339 was identified to be related to the PR #104562 that attempted to fix this issue.

  6. melvin-bot commented on Oct 29, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  7. melvin-bot commented on Oct 29, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  8. self-assigned this
    on Oct 29, 2026
  9. changed the title [-][$250] [Approve Travel R1] Trips table in Spend[/-] [+][Due for payment 2026-11-05] [$250] [Approve Travel R1] Trips table in Spend[/+] on Oct 29, 2026
  10. melvin-bot commented on Oct 29, 2026

    @melvin-bot

    @suneox

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.25-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-11-05. 🎊

    Contributor+ Checklist: The following checklist (instructions) needs to be completed before this issue can be closed:

    • [@suneox] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

    If no checklist is needed for this issue, use the K2 [no checklist button].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions