[HOLD for payment 2023-07-28] Payment method not sticky in the expenseReport view.

[trjExpensify]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

policyExpenseChat beta to have access to the workspace chats.

1. As the member, create a request for $50.00 > send it to a workspace
2. As the admin of the workspace change the settlement method from Pay with Expensify to Pay elsewhere
3. Pay the report
4. As the member, create another request for $50.00 > send it to the same workspace
5. As the admin of the workspace, navigate to the member's workspace chat
6. Observe the pay button in the report preview displays Pay elsewhere ✅
7. Click on the report preview to navigate to the expense report
8. Observe the pay button in the header displays Pay with Expensify ❌

Expected Result:

The Pay elsewhere settlement method should have been displayed in the expenseReport view as it's "sticky" and it was the last settlement method used by the admin.

Actual Result:

The pay button in the expenseReport header incorrectly displayed as Pay with Expensify

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: v1.3.38-4
Reproducible in staging?: Y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

WQPWKegZCi.mp4

Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C02HWMSMZEC/p1688744493384329?thread_ts=1688476481.516029&cid=C02HWMSMZEC

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0156192fdb8e16398b
• Upwork Job ID: 1678491715975114752
• Last Price Increase: 2023-07-10

[melvin-bot]

Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0156192fdb8e16398b

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @fedirjh (Internal)

[trjExpensify]

@mountiny you're jumping on this one right?

[mountiny]

Yep, had problems with local vm yesterday. Will aim to make a pr today