You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The merchant is defaulted to 'Request' when it is emptied
Actual Result:
The merchant is not defaulted to 'Request'. It is defauled to data that is set in Step 2
The behavior here is that it defaults to whatever data that is entered in the Merchant field when the IOU is created. But what if I need to delete the Merchant and change it back to default (Request), it does not allow me to set it back to 'Request'
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome
MacOS / Desktop
Version Number: 1.3.59-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
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:
Expected Result:
The merchant is defaulted to 'Request' when it is emptied
Actual Result:
The merchant is not defaulted to 'Request'. It is defauled to data that is set in Step 2
The behavior here is that it defaults to whatever data that is entered in the Merchant field when the IOU is created. But what if I need to delete the Merchant and change it back to default (Request), it does not allow me to set it back to 'Request'
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.59-0
Reproducible in staging?: Yes
Reproducible in production?: No
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
Bug6182657_20230830_201332.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: