-
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-03-17] Fix broken logic in isIOUOwnedByCurrentUser #15390
Comments
@luacmartins Whoops! This issue is 2 days overdue. Let's get this updated quick! |
PR is in review! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.81-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-03-17. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
This issue was reported, worked on and reviewed internally. So no payments are due. Closing it! |
Problem
The logic in
isIOUOwnedByCurrentUser
is broken, since it always returns false ascurrentUserLogin
is an object containing user login information and not the user email.Additionally, this line always returns true for
!report.isIOUReportOwner
sinceisIOUReportOwner
is not a property of the report object.Why is this important
Broken logic results in unexpected behavior
Solution
Fix it
The text was updated successfully, but these errors were encountered: