-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2024-04-05] Web - Expense report - Approve button not disabled if selected before enabling Self-approval #38889
Comments
👋 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:
|
Triggered auto assignment to @francoisl ( |
We think that this bug might be related to #wave-collect - Release 1 |
We think that this bug might be related to #wave-collect - Release 1 |
Seems to have come from #37348 |
Guessing it's not a blocker since collect policies are not available to users on NewDot yet. @barros001 @alitoshmatov - looks like it might be coming from #37348 indeed – any idea on how we could fix this? |
@francoisl I'll look into it as soon as I can and report back. By looking at the video (I have not had a change to look at code yet), I have a quick question: Under what circumstances would we want to have the Pay buttons visible/active while Approve is disabled? I raised this question while working on the original issue but we decided not to touch that logic as it was out of scope and we didn't want to break anything. If we really want to keep them there, then we'd have to make it so the button itself is disabled but then dropdown button (caret) is not so you can click and pick a different option. |
PR open for review. It assumes we do not want to touch the show/hide payment buttons logic and it only deals with the approve button. |
Here's a video of how it behaves: Screen.Recording.2024-03-25.at.5.50.42.PM.mov |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-04-05. 🎊 |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
All done here, fix is on production. The regression was fixed by the author of the PR that originally caused it, so I believe no payment is needed, but let me know if that's wrong. |
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: 1.4.56-1
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #37348
Issue reported by: Applause - Internal Team
Action Performed:
precondition: user created a collect policy in OD, added a bank account, and set Direct reimbursements
Expected Result:
The approve button is disabled both on the report preview and in the expense report
Actual Result:
The approve button is not disabled if it was selected before enabling Self-approval. Clicking on the Approve button results in skeleton loading
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6424411_1711211397899.Recording__345.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: