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.

Sign up for GitHub

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

Jump to bottom

[Search v2.3] [App] Update the Search LHN to include saved searches #48454

Closed

lakchote opened this issue Sep 3, 2024 · 10 comments

Assignees

Labels

Engineering Reviewing Weekly

Contributor

lakchote commented Sep 3, 2024 •

edited by luacmartins

Loading

We need to update the Search LHN to include saved searches.

More details can be found here

Issue Owner

Current Issue Owner: @lakchote

lakchote added Engineering Weekly labels

lakchote assigned lakchote and luacmartins

lakchote added this to [#whatsnext] #expense

lakchote moved this to Release 3: Fall 2024 (Nov) in [#whatsnext] #expense

lakchote changed the title ~~[Search v2.3] [App] Update the Search LHN to include saved searches~~ [HOLD Auth #425359] [Search v2.3] [App] Update the Search LHN to include saved searches

lakchote mentioned this issue

[Search v2.3] [App] Implement Saved Search feature #48566

Merged

71 tasks

melvin-bot bot added Reviewing Weekly and removed Weekly labels

lakchote changed the title ~~[HOLD Auth #425359] [Search v2.3] [App] Update the Search LHN to include saved searches~~ [Search v2.3] [App] Update the Search LHN to include saved searches

melvin-bot bot commented Sep 14, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 14, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 15, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 15, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 15, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 15, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 15, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 15, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

melvin-bot bot commented Sep 16, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

Contributor

luacmartins commented Sep 19, 2024

This is done

luacmartins closed this as completed

github-project-automation bot moved this from Release 3: Fall 2024 (Nov) to Done in [#whatsnext] #expense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment