-
Notifications
You must be signed in to change notification settings - Fork 139
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
New Component: FilterPanel #4477
Labels
area: migration ➡️
Migration of Security package to IBM Products
Comments
elycheea
added
the
area: migration ➡️
Migration of Security package to IBM Products
label
Mar 7, 2024
github-project-automation
bot
moved this from In progress
to Done 🚀
in Carbon for IBM Products
Mar 21, 2024
2 tasks
2 tasks
github-project-automation
bot
moved this from In progress
to Needs triage 🧐
in Carbon for IBM Products
Mar 25, 2024
github-project-automation
bot
moved this from In progress
to Done 🚀
in Carbon for IBM Products
Mar 26, 2024
github-project-automation
bot
moved this from Done 🚀
to Needs triage 🧐
in Carbon for IBM Products
Mar 26, 2024
Closed
2 tasks
2 tasks
github-project-automation
bot
moved this from Backlog 🌋
to Done 🚀
in Carbon for IBM Products
Mar 29, 2024
github-project-automation
bot
moved this from Done 🚀
to Needs triage 🧐
in Carbon for IBM Products
Apr 1, 2024
2 tasks
2 tasks
github-project-automation
bot
moved this from Needs triage 🧐
to Done 🚀
in Carbon for IBM Products
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FilterPanel
Please refer to #4052 for more details about migrating legacy Security components to Products v2.
Brief description
Migrate FilterPanel and all its subcomponents from
Products v1 / Security / FilterPanel
to Products v2.Refer to Tasks below for subcomponent details.
References: GitHub, Storybook.
For migration purposes:
v2
must match versionv1
exactly.Tasks
Before starting work on this epic, please review and complete the following.
Working in Carbon for IBM Products package
Tasks
The text was updated successfully, but these errors were encountered: