-
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-10-14] [HOLD for payment 2024-10-11] [$250] [Search v2.4] [App] Add Recent Searches and Recent Chats sections #49116
Comments
Triggered auto assignment to @Christinadobrzyn ( |
Hey! I’m Jakub Szymczak from Software Mansion, an expert agency, and I’d like to work on this issue! |
Job added to Upwork: https://www.upwork.com/jobs/~021834650319760395608 |
Current assignee @rayane-djouah is eligible for the External assigner, not assigning anyone new. |
@luacmartins, @Christinadobrzyn, @rayane-djouah, @SzymczakJ Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
hi @SzymczakJ do you have an update on this for the team? TY! |
The draft PR should be ready tomorrow. |
@luacmartins, @Christinadobrzyn, @rayane-djouah, @SzymczakJ Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Draft PR up |
Monitoring - #49457 |
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. |
Hey @rayane-djouah and @SzymczakJ can you check these ^ deploy blocker messages to see if they apply here? |
but @jasperhuangg removed the deploy blocker labels from the issue as they were not able to reproduce it. |
Those blockers apply here, but they were already fixed with this PR/CP, that's why the blocker label was removed |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.44-12 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-10-11. 🎊 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:
|
Regression tests will be handled as part of the project wrap-up |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.45-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-10-14. 🎊 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:
|
Regression tests will be handled as part of the project wrap-up |
Payouts due:
|
@Christinadobrzyn - Offer accepted, thank you! |
Payment Summary
BugZero Checklist (@Christinadobrzyn)
|
It's payday - payment summary here - #49116 (comment) No regression test so closing this out. |
Implement this section of the doc
cc @Kicu @289Adam289 @Guccio163 @SzymczakJ
Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ChristinadobrzynThe text was updated successfully, but these errors were encountered: