-
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
[HOLD for payment 2023-10-24] [$500] Workspace - Admin Checkbox in Members Section Ticked When Changing Contact Method #28539
Comments
ProposalPlease re-state the issueAble to select the policy owner after changing the contact method. What is the root cause of this issue?While checking whether an option should be disabled, we are setting the
But the What changes do you think should be made to fix this problem?We should convert the isDisabled: Number(accountID) === props.session.accountID || details.login === props.policy.owner || policyMember.pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE, What other alternative options did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~01ccfbef1a9c9e1edd |
Triggered auto assignment to @alexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Workspace - Admin Checkbox in Members Section Ticked When Changing Contact Method What is the root cause of that problem?When we change the contact method,
What changes do you think we should make in order to solve the problem?Instead of compare
What alternative solutions did you explore? (Optional)In |
@parasharrajat - when you get a chance can you review if one of these proposals will resolve this issue? Thanks! |
@parasharrajat any update here? |
Started reviewing... |
Triggered auto assignment to @marcaaron, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Marc is OOO but will review soon. If Marc is unable to help, I'll find help to keep it moving forward. |
Not sure why the cc @puneetlath I think this change was first introduced here in case you have some idea. |
Rejected the proposal because:
It looks like we already do this here. |
Passing the 🏀 back to you @parasharrajat 😄 |
Oh duh I see now that the isDisabled logic is set in the same object 🤦 |
I think ideally we can fix this at a lower level instead of cast to a |
@esh-g can you analyze this #28539 (comment)? |
@parasharrajat PR is ready: #29422 💫 |
Yep exactly |
Awesome, looks like the PR is moving forward! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.85-4 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-24. 🎊 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:
|
@parasharrajat - to prepare for the payment date, can you please complete the checklist? Thanks! |
@parasharrajat - please complete the checklist. Thanks! |
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 Steps
Do you agree 👍 or 👎 ? |
@marcaaron - can we confirm if you agree with the regression test above? |
LGTM |
Here is the payment summary:
Upwork Job: https://www.upwork.com/jobs/~01ccfbef1a9c9e1edd *If applicable, the bonuses will be applied on the final payment Extra Notes regarding payment: There is an urgency bonus and hit the 3-day business day mark. |
@tewodrosGirmaA and @esh-g - can you please apply to the link above and I can complete the next steps in Upwork. Not sure what happened but the automation didn't kick in here. Thanks! |
Applied @alexpensify 🚀 |
Applied @alexpensify |
Thanks! I need your approval in Upwork, and then can complete the process. |
Accepted the offer @alexpensify |
Everyone has been paid via Upwork. @parasharrajat please submit your request too. Thanks! |
Alright, the regression test has been created so I'm going to close out the issue. Great work here! |
Payment requested as per #28539 (comment) |
$750 payment approved for @parasharrajat based on this comment. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Changing the contact method should not cause the Admin checkbox to be ticked in the Members section.
Actual Result:
Changing the contact method causes the Admin checkbox to be ticked in the Members section.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.73.0
Reproducible in staging?: y
Reproducible in production?: y
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
Recorder_30092023_183937.mp4
Recorder_30092023_161410.mp4
Recorder_30092023_085849.mp4
Screen.Recording.2023-09-29.at.10.38.26.PM.mov
Recording.1631.mp4
screen-capture.-.2023-09-22T140546.004.webm
screen-capture.5.mp4
Expensify/Expensify Issue URL:
Issue reported by: @tewodrosGirmaA
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695415622144909
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: