-
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-23] [HOLD for payment 2023-10-23] [HOLD for payment 2023-09-29] [Wave 6: Tags] CRITICAL - Billable Toggle UI #26128
Comments
Triggered auto assignment to @puneetlath ( |
Convenient auto-assignment 😄 (feel free to unassign if you don't want to be assigned though) Callstack will be helping here! |
Hello, Im Artem from Callstack, can I help with this one? |
Thanks @waterim! Could you provide an ETA on when you think you'll be able to have a PR up? Also, do you plan to tackle everything in one PR? Or break it up in some way? |
Hello @puneetlath I think I will have enough capacity tomorrow and Friday to create a PR for this feature |
Ok sounds good. Looking forward to it! |
hey @waterim just checking in on how this is going. Do you need any help? |
Hey @puneetlath |
Ok sounds good! |
Just curious @amyevans can |
Hello @puneetlath, I have a question regarding this |
@jeet-dhandha Not usually, but it isn't a hard and fast rule. Keep your eye out in the #expensify-open-source channel in Slack where internal engineers would likely recruit external help as needed (in addition to applying the |
@puneetlath @amyevans PR is opened :) |
@0xmiroslav think you'll have a chance to review today? |
Oh, I didn't know that all feedback is addressed already. Reviewing now |
Awesome, thanks! |
@amyevans I can add to the same PR, because thats bot a lot of changes and PR will not be huge Sorry, I didn’t know that DistanceRequest requires billable as well(in documentation it was only for money request) |
Sounds good, and no worries! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.72-11 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-09-29. 🎊 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:
|
Looks like we just need to pay out @0xmiroslav for C+ on this. @0xmiroslav should I send you an Upwork contract or will you track this separately for yourself? |
I am tracking so let's close for now. Thanks |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-23. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-23. 🎊 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:
|
Reminder: only users in the beta will have the data
Design doc section
The text was updated successfully, but these errors were encountered: