-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[PAID] [$500] Workspace - Unable to remove error reported member #26339
Comments
Triggered auto assignment to @strepanier03 ( |
Bug0 Triage Checklist (Main S/O)
|
Hmmm, I do not have the same experience when trying to repro this. Following the steps from the recording on Android/Chrome (Pixel 6), I do not have the option to select an invalid phone number at all. I tried entering just "84" as the video and I have to enter a full phone number to be able to select anything. When I do, the number is valid and I don't get the error report as described. |
@lanitochka17 - Anything different in your setup that isn't covered in the bug report? Can you still repro? |
@strepanier03 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Okay finally got it, thanks @lanitochka17. I was able to repro just fine using the new number you provided. Moving on. |
Job added to Upwork: https://www.upwork.com/jobs/~011d44b0b1f472370a |
Current assignee @strepanier03 is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Workspace - Unable to remove error reported member What is the root cause of that problem?Firstly, In App/src/pages/workspace/WorkspaceMembersPage.js Lines 235 to 244 in 57b7606
we use
Secondly, In App/src/libs/actions/Policy.js Lines 749 to 756 in 57b7606
we use What changes do you think we should make in order to solve the problem?Firstly, we need to add accountID to result
Secondly, we need to change App/src/libs/actions/Policy.js Lines 749 to 756 in 57b7606
to
like what we did in ResultScreen.Recording.2023-09-06.at.19.21.11.mov |
ProposalPlease re-state the problem that we are trying to solve in this issue.We can't remove failed-to-add workspace members. What is the root cause of that problem?There are 2 issues. First, to delete a user from the workspace member list, we need the App/src/pages/workspace/WorkspaceMembersPage.js Lines 235 to 244 in db1a306
App/src/pages/workspace/WorkspaceMembersPage.js Lines 308 to 309 in db1a306
Second, even if we pass the correct account ID, the member is never deleted from Onyx. In App/src/libs/actions/Policy.js Lines 749 to 756 in db1a306
However, we currently have an issue where setting null as the value won't really clear it from the Onyx. What changes do you think we should make in order to solve the problem?
|
Happy to go with @tienifr's proposal. The RCA is correct and the solution makes sense. I think we can just use the existing @bernhardoj's proposal is almost the same, except they propose to wait for the Onyx issue to be resolved, which we don't have a timeline for so it makes sense to just fix now. We also already do the same here: App/src/libs/actions/Policy.js Lines 734 to 741 in db1a306
🎀👀🎀 C+ reviewed |
Triggered auto assignment to @dangrous, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Yep, I agree with that, I'll assign you @tienifr! Just to confirm, once that Onyx issue IS fixed, will we need any modifications to this code, or will this work as expected? I think it will be fine, but wanted a second opinion. |
📣 @jjcoffee 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
Ah great find, thanks! I think we can hold on Expensify/react-native-onyx#359 then cc @dangrous |
#359 got merged :) |
I'll re-test soon |
Sweet! @tienifr can you test react-native-onyx 1.0.89 in your PR and see how it goes? |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 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 2023-10-09. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue: As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
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
Do we agree 👍 or 👎 |
@strepanier03 Checklist complete - sorry for the delay! Also, I think this may be due the timeliness bonus as we ended up needing to hold for a react-native-onyx update. After that update came, our PR was merged within 3WD. |
@jjcoffee - No worries on the checklist, we're all busy and it was done pretty quickly still anyway. Thanks for the heads-up on the Onyx changes. I'll review the timeline and update the payment post with a final determination. If we apply the bonus, I'll add an additional payment for the contributor as well to make things square. Will update you soon! |
Timeline:
@jjcoffee - Can you give me some context regarding when the PR was first put on hold? Was it created under the assumption it would be on hold right away because of the Onyx work? I think that it was likely before 2023-09-12 when a hold comment was left on the PR. If that's the case I want to consider that in my review. Thanks! |
@strepanier03 Sure! We actually thought the Onyx fix would take a while to come together so the plan was to add a temporary fix in the PR and then revert once the Onyx change was ready. Those Onyx changes came earlier than expected so we didn't need that initial workaround PR in the end and just decided to hold until the Onyx changes got merged. |
Thank you so much for that context. I'm going to update this for the urgency bonus and appreciate you raising it and discussing it with me. I'll finish updating this now. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
The workspace members page must not display error reported member which is removed
Actual Result:
The workspace members page displays removed error reported member again after refreshing the page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.59
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6183139_remove.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: