-
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
[Search v2.2] [App] Create Chat contextual filter #46587
Comments
@luacmartins Huh... This is 4 days overdue. Who can take care of this? |
Still waiting on doc reviews. |
@luacmartins Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@shubham1206agra will be taking on the implementation! |
Triggered auto assignment to @zanyrenney ( |
@shubham1206agra do you mind please updating this issue according to the KSV2 cadence? |
Actively working on this. I am waiting on #47181. |
Thanks for the update @shubham1206agra |
We're waiting on the issue linked above by @shubham1206agra |
Issues linked above yesterday! |
Just a heads up, I am going OOO until August 30th. I won't reapply the bug label as we're far from payout, but please can you keep this issue updated daily with your progress @shubham1206agra also, @luacmartins, can you confirm what the day for the payout should be, please? Some of the issues were merged 4 days ago but some still in draft so not sure how we should be counting this one. Thanks! |
This is still being worked on, so we don't have a date yet. The linked issues/PRs were related to this issue, but weren't directly implementing these changes. |
@luacmartins, @ikevin127, @zanyrenney, @shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Waiting on #47753 to merge |
@shubham1206agra PR merged, let's keep up the work on this issue |
@luacmartins, @ikevin127, @zanyrenney, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@shubham1206agra is still working on the PR (I think), tried to help move it forward in #47690 (comment) with my investigation of the current blocker, but the author replied:
I think in order to move this forward we either have to ask the author if they have capacity to actually work on this and move it along to open the PR, or with author's approval, ask somebody else to work on the issue and open the PR. cc @luacmartins |
@ikevin127 I asked you to help me on #47690 (comment) since I am unable to find any fix yet. And this is the only blocker for the PR. Can you please help me with this? Edit - This is fixed now. I will open the PR shortly. |
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. |
We'll handle payment for this in #46588. |
Implement this section of the design doc
Issue Owner
Current Issue Owner: @shubham1206agraThe text was updated successfully, but these errors were encountered: