Repository navigation
[HOLD for payment 2023-12-18] [HOLD for payment 2023-12-15] [$125] WS - Email of the newly added user appears in the find member field+all other members disappear #32635
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: v1.4.9-1
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause-Internal Team
Slack conversation: @
Action Performed:
- Go to URL https://staging.new.expensify.com/
- Login with any account
- Go to Settings -> Workspaces -> Open any WS -> Members -> Invite
- Using the paste option or CTRL-V paste the user email you just saved (can change it) -> Choose this user -> tap Next -> Invite
Expected Result:
The member search field remains empty.
Members do not disappear from the WS list.
Actual Result:
The email of the newly added user appears in the find member field.
All other members disappear, including the admin.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Bug6303879_1701912933776.bandicam_2023-12-07_02-47-24-182.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01f603e8abe151eada
- Upwork Job ID: 1732686658700615680
- Last Price Increase: 2023-12-07
- Automatic offers:
- aimane-chnaif | Contributor | 27995826
Activity
[-]WS - Email of the newly added user appears in the find member field+all other members disappear[/-][+][$500] WS - Email of the newly added user appears in the find member field+all other members disappear[/+]melvin-bot commentedon Dec 7, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01f603e8abe151eada
melvin-bot commentedon Dec 7, 2023
Triggered auto assignment to @alexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Dec 7, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)melvin-bot commentedon Dec 7, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (
External)24 remaining items
[-][$125] WS - Email of the newly added user appears in the find member field+all other members disappear[/-][+][HOLD for payment 2023-12-15] [$125] WS - Email of the newly added user appears in the find member field+all other members disappear[/+]melvin-bot commentedon Dec 8, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 8, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.9-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 2023-12-15. 🎊
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:
melvin-bot commentedon Dec 8, 2023
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:
aimane-chnaif commentedon Dec 8, 2023
I think we can close this. The contributor's solution was not actually used. #32638 (comment)
mountiny commentedon Dec 8, 2023
Ok thanks
[-][HOLD for payment 2023-12-15] [$125] WS - Email of the newly added user appears in the find member field+all other members disappear[/-][+][HOLD for payment 2023-12-18] [HOLD for payment 2023-12-15] [$125] WS - Email of the newly added user appears in the find member field+all other members disappear[/+]melvin-bot commentedon Dec 11, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.10-1 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-12-18. 🎊
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:
melvin-bot commentedon Dec 11, 2023
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: