-
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 2024-08-05] Improve filtering performance in task share page #46151
Comments
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach ( |
Triggered auto assignment to @zanyrenney ( |
@TMisiukiewicz please comment for assignment and link #40290 to this issue before opening it up for review. Thanks |
Thank you @roryabraham, linked the issue and opened a PR |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.13-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 2024-08-05. 🎊 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:
|
Payment Summary
BugZero Checklist (@zanyrenney)
|
This is part of another PR
NA
NA
Regression test proposal
Do we agree 👍 or 👎 |
Looks good, thanks @ZhenjaHorbach |
there seems to be no existing upwork job, reapplying the label to retrigger |
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue. |
Current assignee @ZhenjaHorbach is eligible for the External assigner, not assigning anyone new. |
@ZhenjaHorbach invited you to the upwork job, please accept for payout. |
Done, Thank you ! |
hired! accept for payout please @ZhenjaHorbach |
Done ! |
Payment Summary
|
This issue is branched off of #37619 and was created specifically to manage the lifecycle and payments of this PR: #40290
Issue Owner
Current Issue Owner: @The text was updated successfully, but these errors were encountered: