Repository navigation
[$250] Expense - Pay with Expensify button appears for Employee after admin disconnects bank account #46738
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.16-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: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
- Delayed submission is enabled in Workflows
- Workspace has an approver (admin)
- Workspace has set up with bank account
- Employee does not have bank account
- Go to staging.new.expensify.com
- [Employee] Go to workspace chat
- [Employee] Submit an expense over $100
- [Employee] Click on the submit button and stay on the main chat
- [Admin] Click Approve button on the expense preview
- [Admin] Go to workspace settings > Workflows
- [Admin] Click on the bank account
- [Admin] Disconnect bank account
- [Employee] Note that "Pay with Expensify" button shows up on expense preview on employee end after admin has disconnected bank account
Expected Result:
"Pay with Expensify" button will not appear on expense preview on employee end after admin has disconnected bank account
Actual Result:
"Pay with Expensify" button shows up on expense preview on employee end after admin has disconnected bank account.
When clicking on the expense preview and returning to main chat, the button disappears
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Bug6560213_1722605179858.20240802_211830.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01e26750961886bca4
- Upwork Job ID: 1821153286159845456
- Last Price Increase: 2024-08-28
- Automatic offers:
- jjcoffee | Reviewer | 103796028
Issue Owner
Current Issue Owner: @teneetoMetadata
Metadata
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Aug 2, 2024
Triggered auto assignment to @miljakljajic (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.lanitochka17 commentedon Aug 2, 2024
@miljakljajic FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
lanitochka17 commentedon Aug 2, 2024
We think that this bug might be related to #wave-collect - Release 1
melvin-bot commentedon Aug 5, 2024
@miljakljajic Whoops! This issue is 2 days overdue. Let's get this updated quick!
[-]Expense - Pay with Expensify button appears for Employee after admin disconnects bank account[/-][+][$250] Expense - Pay with Expensify button appears for Employee after admin disconnects bank account[/+]melvin-bot commentedon Aug 7, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01e26750961886bca4
melvin-bot commentedon Aug 7, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (
External)91 remaining items
melvin-bot commentedon Nov 11, 2024
This issue has not been updated in over 15 days. @twisterdotcom, @teneeto, @jjcoffee, @srikarparsi eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
srikarparsi commentedon Jan 6, 2025
I'll try to get to this next week. In the meanwhile, do you know if there's a room that this would fit into by any chance @puneetlath?
#quality?puneetlath commentedon Jan 6, 2025
#quality sounds good to me @srikarparsi
srikarparsi commentedon Jan 15, 2025
Will try to get to this next week.
muttmuure commentedon Jan 20, 2025
Going to make this MEDIUM as it's a subset of users impacted by this flow. I know it's a mainline case, but the number of steps involved seem to make it less applicable as a CRITICAL issue.
Please let me know if you disagree
melvin-bot commentedon Jan 24, 2025
@twisterdotcom, @teneeto, @jjcoffee, @srikarparsi, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.