Closed techievivek closed 2 months ago
Job added to Upwork: https://www.upwork.com/jobs/~014e28879d82637e16
Triggered auto assignment to @isabelastisser (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rayane-djouah (External
)
We'd like to prevent requesting money from domain emails
There's no logic to exclude domain emails when getOptions
Add a param includeDomainEmail
to getOptions
https://github.com/Expensify/App/blob/57e5d0e7197a9c21e6f221389bed87870c90ef0a/src/libs/OptionsListUtils.ts#L1769, default to true
&& (includeDomainEmail || !Str.isDomainEmail(detail.login))
[Optional] In https://github.com/Expensify/App/blob/57e5d0e7197a9c21e6f221389bed87870c90ef0a/src/libs/OptionsListUtils.ts#L1915 add
if (Str.isDomainEmail(login) && !includeDomainEmail) {
return;
}
In the money request participants page, pass includeDomainEmail
as false
Can include the same check in other places in getOptions
if needed
includeDomainEmail=false
can be used for other use cases that should not include the domain email. We can also default includeDomainEmail
to false
if we don't want to show this when getting options by default.
We can optionally update the message when not found to "You cannot submit expense to a domain email". It's clearer than "No results found" that's being shown to the user.
@nkdengineer's proposal looks good to me.
:ribbon::eyes::ribbon: C+ reviewed
Current assignee @techievivek is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.
@techievivek - To confirm, Do we need to exclude domain email options in all IOU flows: Submit Expense, Split Expense, Pay Someone, Send Invoice? Do we also need to exclude them in the Start chat and assign task flows?
Edit: based on this issue https://github.com/Expensify/App/issues/44485, we need to exclude the domain email option for the Start chat flow. So, I think all flows should be considered.
So, I think all flows should be considered.
Yeah, we want to exclude them from all the flows as as they are not real users.
📣 @rayane-djouah 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻 Keep in mind: Code of Conduct | Contributing 📖
Whatever we do here, we will ALSO need to update the backend @techievivek
@rayane-djouah this PR is ready for preview
@iwiznia Yeah, backend already handles this exception correctly.
@nkdengineer @techievivek did the PR for this also take care of preventing starting a chat, a group, assigning a task, inviting to a workspace.. basically filtering the domain account out of the participant selector everywhere?
@trjExpensify Yeah, we have handled this for all cases; C+ confirmed this here: https://github.com/Expensify/App/issues/44429#issuecomment-2192166488.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.5-13 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-07-17. :confetti_ball:
For reference, here are some details about the assignees on this 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:
@trjExpensify Yeah, we have handled this for all cases; C+ confirmed this here: #44429 (comment).
Great stuff!
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.6-8 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-07-22. :confetti_ball:
For reference, here are some details about the assignees on this 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:
Bump @rayane-djouah to complete the BZ list, thanks!
The payments were processed in Upwork.
Triggered auto assignment to @adelekennedy (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
I will be OOO tomorrow and next week, so I am reassigning this until I return on July 29. Thanks, @adelekennedy!
Status:
Regression Test Proposal
+@<domain>
, like +@applause.expensifail.com
.Do we agree 👍 or 👎
The regression test looks good to me; @adelekennedy, can we please get that added? Thanks.
Not overdue, completing the BZ list.
@isabelastisser, @techievivek, @adelekennedy, @rayane-djouah, @nkdengineer Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Thanks, @adelekennedy !
Domain emails are in format
+@<domain>
like+@expensify.com
.Problem
We allow users to request money from domains in newDot. Update the code so we don't allow this action.
Steps to reproduce:
Split expense
.+@applause.expensifail.com'
and confirm you are able to select that email as an option.Solution
Update the code to prevent users from requesting money from domain emails.
Solution
Update the code to prevent users from requesting money from domain emails.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @isabelastisser