-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] Pay someone - Unapprove option is available for "Pay someone" expense, which gives error #44966
Comments
Triggered auto assignment to @MitchExpensify ( |
Triggered auto assignment to @johnmlee101 ( |
👋 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:
|
@johnmlee101 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 |
We think that this bug might be related to #vip-vsb |
@rushatgabhane looks like we gotta fix this! |
PR up soon |
Fix merged & CPing |
Done 'n dusted, should be fixed as of |
Can we please reopen to complete payment for PR #45049 |
There's 3 app PRs listed in that PR, we only need to handle payment in 1 of those - so I was thinking we'll do that in a different one, not this one |
@Beamanator Can we reopen any of those please : D |
Aah yep looks like @ishpaul777 hasn't been paid for reviewing #45049 🙏 @MitchExpensify can you please help with that? 🙏 |
asked for payment help internally |
Job added to Upwork: https://www.upwork.com/jobs/~010702f689c6b7150e |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Pujan92 ( |
ah.. shit, sorry @Pujan92 , forgot to assign @ishpaul777 BEFORE adding @ishpaul777 can you please accept the job and reply here once you have? |
I have accepted the offer 🙏 Thank you! @mallenexpensify |
Contributor+: @ishpaul777 paid $250 via Upwork. @ishpaul777 we want a regression test for this, right? Assuming so, can you fill out the checklist? Thx BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Regression Test proposal -
Expected Result:Unapprove option should not be available for "Pay someone" expense report. Do we agree 👍 or 👎 ? |
Thanks @ishpaul777 test case GH created |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.5-2
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Expected Result:
Unapprove option should not be available for "Pay someone" expense.
Actual Result:
Unapprove option is available for "Pay someone" expense, which results in error.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6535832_1720443170610.20240708_205102.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Pujan92The text was updated successfully, but these errors were encountered: