-
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
[HOLD for payment 2023-11-18] [$500] Deleting all workspaces does not remove red dot #29235
Comments
Job added to Upwork: https://www.upwork.com/jobs/~013278e8038908746f |
Triggered auto assignment to @NicMendonca ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Deleting all workpsaces doesnt remove the red dot from the avatar and the settings workpsace tap What is the root cause of that problem?in this line we dont check if the current admin policies are empty or beside the reimbursementAccount.errors check App/src/pages/settings/InitialSettingsPage.js Lines 180 to 181 in 7f7b424
same for the avatar indicator App/src/components/Indicator.js Line 82 in 0cbee22
What changes do you think we should make in order to solve the problem?Get the admin typed workspaces and check if they are empty or not beside reimbursementAccount.errors check const adminPolicies = _.chain(props.policies)
.filter((policy) => policy && policy.type === CONST.POLICY.TYPE.FREE && policy.role === CONST.POLICY.ROLE.ADMIN)
.value(); change the check to: (!_.isEmpty(props.reimbursementAccount.errors) && !_.isEmpty(adminPolicies)) || also in the indicator component we do the same .. const adminPolicies = _.chain(cleanPolicies)
.filter((policy) => policy && policy.type === CONST.POLICY.TYPE.FREE && policy.role === CONST.POLICY.ROLE.ADMIN)
.value(); () => !_.isEmpty(adminPolicies) && !_.isEmpty(props.reimbursementAccount.errors), POCScreen.Recording.2023-10-11.at.1.30.13.AM.mov |
ProposalPlease re-state the problem that we are trying to solve in this issue.App displays red dot of workspace error even after we delete all the workspaces, it removes the red dot on relogin What is the root cause of that problem?We're not clearing the errors from the reimbursementAccount after all workspaces are deleted. So the red dot will still show in the "Workspaces" in settings in this condition and still show in user avatar in this condition The What changes do you think we should make in order to solve the problem?In What alternative solutions did you explore? (Optional)NA |
forgot to mention that by making those changes, whenever we create a new workspace again after we delete all of them, the red dot will be back again, which i think is the expected behavior. |
Just IMO I'd be quite surprised if an error comes out of nowhere once I create a new workspace 😄 |
@abzokhattab @dukenv0307 I'm asking on slack here https://expensify.slack.com/archives/C01GTK53T8Q/p1697023569138709 Would love to hear your voice there. Thanks |
@hoangzinh, hey from here it's mentioned that there is proper separation between workspace's bank account hence we should do the same thing in error also right? i.e. workspace's based error. |
@Charan-hs Sorry, I don't get it. Could you clarify it again? Thanks |
@hoangzinh |
@Charan-hs The PR you mentioned is closed. It looks like we still keep the previous behavior, the bank account will shared for all workspaces. |
What is the final verdict on here? which approach should we take? @hoangzinh |
@abzokhattab According to discussion here https://expensify.slack.com/archives/C01GTK53T8Q/p1697045876921169?thread_ts=1697023569.138709&cid=C01GTK53T8Q We're expecting the bank account's error will be cleared out completely once we delete all workspaces |
@abzokhattab Thanks for your proposal #29235 (comment). But according to our expectation above #29235 (comment), your RCA is not totally correct, thus the solution won't solve the root cause. |
@dukenv0307 Thanks for your proposal #29235 (comment). Your solution looks great. But can you add more details to your RCA? It's hard to understand why |
Proposal updated to add more detailed RCA, thank you for the feedback! |
@dukenv0307 thanks for updating. Your proposal has a correct RCA and also provided a solution that fits with our expectation here https://expensify.slack.com/archives/C01GTK53T8Q/p1697045876921169?thread_ts=1697023569.138709&cid=C01GTK53T8Q Thus, I think we go with @dukenv0307's proposal #29235 (comment) 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @luacmartins, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @hoangzinh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @dukenv0307 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @dhanashree-sawant 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
Assigning @dukenv0307 to the issue! |
@hoangzinh The PR is ready for review. |
Hey team @dukenv0307 @luacmartins @NicMendonca , just wanna raise a recent change of Workspace bank account error here #27901 (comment). After that issue, our issue can not be reproduced anymore (because the Workspace bank account's error will be cleared when the user closes RHN). But It can be reproduced by another way as @dukenv0307 described in his PR #29781 (comment)
Just wanna discuss whether we should continue to fix this issue with those new steps |
@hoangzinh do we have a video of what that looks like? Might help with deciding if we should still fix this |
sure. Those are recordings
Screen.Recording.2023-10-26.at.23.32.50.-.before.mov
Screen.Recording.2023-10-26.at.23.31.20.-.after.mov
Screen.Recording.2023-10-26.at.23.31.58.-.new.mov |
cc @luacmartins @NicMendonca waiting for your thoughts on the comment above ^. |
Thanks for the videos @hoangzinh! Yea, I think we should still fix this. |
It looks like Melvin didn't process the next step for this issue. The PR #29781 has been deployed to PROD 10/11/2023 |
BugZero Checklist:
|
omg, sorry, this didn't pop open as a daily for me to pay |
Everyone has been paid via Upwork 🎉 |
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.3.80-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696933257327709
Action Performed:
Expected Result:
App should remove red dot of workspace error if we delete all the workspaces
Actual Result:
App displays red dot of workspace error even after we delete all the workspaces, it removes the red dot on relogin
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
android.chrome.red.dot.error.not.removed.after.workspace.delete.mp4
iOS: Native
iOS: mWeb Safari
ios.safari.red.dot.not.removed.after.workspace.delete.mov
MacOS: Chrome / Safari
mac.chrome.red.dot.not.dismissed.even.on.all.workspace.delete.mov
Red.dot.mp4
MacOS: Desktop
mac.desktop.red.dot.not.dismissed.even.on.all.workspace.delete.mov
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: