-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Enable showing integration subcategories #153591
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jen-huang
added
release_note:enhancement
backport:skip
This commit does not require backporting
labels
Mar 23, 2023
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
jen-huang
added
the
Team:Fleet
Team label for Observability Data Collection Fleet team
label
Mar 23, 2023
8 tasks
Pinging @elastic/fleet (Team:Fleet) |
criamico
approved these changes
Mar 29, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Build Succeeded
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @jen-huang |
jgowdyelastic
pushed a commit
to jgowdyelastic/kibana
that referenced
this pull request
Mar 30, 2023
## Summary Now that elastic/integrations#5123 and elastic#153216 is complete, this PR enables the integration subcategories feature by default. Users will see a much shorter list of top-level integration categories when they land in Browse Integrations. Once the user clicks into a category, subcategories will be presented if there are any (see elastic#148894 for more details). With the associated changes now merged and enabling this flag, the list now looks like this initially: ![image](https://user-images.githubusercontent.com/1965714/227375323-bd649342-1deb-4106-aaa5-0e7573574d2d.png) And when clicking into a large category with subcategories: ![image](https://user-images.githubusercontent.com/1965714/227375436-7203aec0-48ee-4861-8a5d-af9ce37dedad.png)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:skip
This commit does not require backporting
release_note:enhancement
Team:Fleet
Team label for Observability Data Collection Fleet team
v8.8.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Now that elastic/integrations#5123 and #153216 is complete, this PR enables the integration subcategories feature by default. Users will see a much shorter list of top-level integration categories when they land in Browse Integrations. Once the user clicks into a category, subcategories will be presented if there are any (see #148894 for more details).
With the associated changes now merged and enabling this flag, the list now looks like this initially:
And when clicking into a large category with subcategories: