-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[$250] Workspace - Error message appears when delete approver #61675
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
Comments
Triggered auto assignment to @RachCHopkins ( |
Triggered auto assignment to @mjasikowski ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
@RachCHopkins 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. |
@RachCHopkins do you think it's a bug? I think it's a valid error and should be shown, but could be worded differently (i.e. "workspace" instead of "policy"). |
@mjasikowski I feel like it's showing in the wrong place though, wouldn't you say? |
This comment has been minimized.
This comment has been minimized.
Actually, I take that back - if you click the box and remove, you get told that the default approver will be the billing owner. And then the approver changes, but they can't be deleted with the check box method. deleteapprover.mp4Also, when you go to add the user and set the default approver again, it takes multiple attempts for the new approver to "stick". You have to go to the workflows page and refresh it first. 2025-05-09_13-52-49.mp4If you come in fresh and you delete the user from the RHP, it DOES delete the user and also reset the approver. So in summary, I have no idea how to repro this OP issue, but it appears there are two more issues:
You should not even be able to delete a default approver, so if that's in a deploy then maybe it is a deploy blocker @yuwenmemon ? |
Thanks @yuwenmemon and @RachCHopkins, I'll see where this is coming from and try to diagnose it. |
Slack discussion here: https://expensify.slack.com/archives/C01GTK53T8Q/p1746998011277749?thread_ts=1746697332.715449&cid=C01GTK53T8Q The gist of this issue is: you shouldn't be able to delete the default approver without it auto-updating to the billing owner. Since it's a front-end thing, I'm marking this issue as external. |
Job added to Upwork: https://www.upwork.com/jobs/~021921856170250657164 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia ( |
Unable to reproduce except for one time but I was offline and got an extra error too. |
I can't reproduce this issue |
Tester can't reproduce the issue either in v9.1.45-7 Recording.5473.mp4 |
@RachCHopkins is it good to close then? |
Not overdue |
Yes, I think so! Closing. |
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: v9.1.41-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6074170&group_by=cases:section_id&group_order=asc&group_id=229065
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Lenovo 80ES / Windows 10 Pro
App Component: Workspace Settings
Action Performed:
Expected Result:
There should be no error message
Actual Result:
Error message "402 default approver is not a member of the policy:" appears under workspace section
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6825385_1746695163820.Recording__5402.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mjasikowskiThe text was updated successfully, but these errors were encountered: