-
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-11-13] [HOLD E/E #326097] [Wave 6: Workspace Chats] Update how GBR is determined for IOU/expense reports #29595
Comments
Current assignee @puneetlath is eligible for the NewFeature assigner, not assigning anyone new. |
Hello, Im Artem from Callstack and would like to help with this one! |
FYI @waterim, from Slack: https://expensify.slack.com/archives/C02MW39LT9N/p1697583395704569?thread_ts=1697503628.240919&cid=C02MW39LT9N It would be nice if we could clean up/centralize the GBR (green dot) logic while we’re doing this. To ensure that:
|
Reminder: we also need to add this new field to the typescript types for reports. |
@waterim FYI we've started sending the |
@puneetlath nice to hear! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.95-9 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-11-13. 🎊 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:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
We should add regression tests for this. I'll propose them. |
Also, @akinwale was the C+ |
Where to add these steps? |
I'll take care of it don't worry. The automation wrongly tagged you for that. |
Actually, we already have a separate issue for handling that here: https://github.com/Expensify/Expensify/issues/319016 So all that is left to happen on this issue is paying @akinwale out next week. |
@akinwale offer here: https://www.upwork.com/nx/wm/offer/27646277 Ping me on this issue when you've accepted please. |
@puneetlath Accepted. Thanks! |
All paid. Thanks everyone! |
In https://github.com/Expensify/Expensify/issues/326097 we are adding a new
hasOutstandingChildIOU
field. We need to update the way ReportUtils.isWaitingForIOUActionFromCurrentUser determines which reports to show the GBR on. It should be based on thehasOutstandingChildIOU
field.This is described in the workspace chats design doc here.
The text was updated successfully, but these errors were encountered: