[Due for payment 2026-06-16] Payment issue for E/App PR#92116

[melvin-bot]

Issue created to compensate the Contributor+ member for their work on #92116
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/642820.
Contributor+ member who reviewed the PR - @truph01.

Wait 7 days after the PR is deployed to production before issuing payment in case there are regressions.

Issue Owner

Current Issue Owner: @truph01

[melvin-bot]

@truph01 The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

@truph01 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Awaiting Payment)

[melvin-bot]

Payment Summary

Upwork Job

• Reviewer: @truph01 owed $250 via NewDot

BugZero Checklist (@mallenexpensify)

• I have verified the correct assignees and roles are listed above and updated the necessary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have verified the PR was not reverted
• I have applied any discounts due to bugs/regressions introduced by this PR
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[mallenexpensify]

Payment Summary

Contributor+: @truph01 due $250 via NewDot

@truph01 plz complete the BZ checklist and tag me in a post once you have. Thx

[truph01]

BugZero Checklist:

• [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to the comment on the PR:
  Link to the comment on the Issue:

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue: https://github.com/Expensify/Expensify/issues/650128

Regression Test Proposal

Precondition:

Test:

1. Open a workspace where Travel is enabled and Travel Invoicing is turned on.
2. Go to Workspace settings → More features.
3. Verify the Travel toggle shows a lock icon and cannot be switched off directly.
4. Press the locked Travel toggle.
5. Verify a modal appears explaining Travel Invoicing must be turned off first.
6. Press the modal's button and verify it navigates to the workspace Travel settings page.
7. Turn Travel Invoicing off, return to More features, and verify the Travel toggle is now interactive and can be turned off.

Do we agree 👍 or 👎

Zapier Logs

Run ID: 00040eee-b2a1-a21c-7f67-d212c4e3b644