App: [$1000] Web - Inconsistent format between Pay elsewhere and other payment method

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:

  1. Login with any account that has multiple pay options (Expensify, Paypal…)
  2. From other account, request money with current account.
  3. From current account, open request money from other account, click on dropdown icon of Pay button.
  4. Observer the pay elsewhere button text.

Expected Result:

All the payment methods should have consistent format

Actual Result:

Other payment methods have the format Pay "number of money" with payment method mean while Pay elsewhere doesn’t have number of money inside it

Workaround:

Unknown

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: 1.3.44.0 Reproducible in staging?: y Reproducible in production?: y 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: Any additional supporting documentation

https://github.com/Expensify/App/assets/93399543/1927d9a0-3b17-4a8c-90b5-5abafde0ddc3

https://github.com/Expensify/App/assets/93399543/86443431-2637-4a4a-a517-489f4ea453ec

Expensify/Expensify Issue URL: Issue reported by: @hungvu193 Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690198255500439

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d6c5423c124afa6d
  • Upwork Job ID: 1684932076793315328
  • Last Price Increase: 2023-08-04

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 16 (6 by maintainers)

Most upvoted comments

I got minimal traction! So far the vote is that this isn’t necessarily a bug, but I will resurface it again next week!