Skip to content
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

Consistent wording for UI in asset groups: Dynamic asset filter or rule #1431

Closed
EllynBsc opened this issue Sep 13, 2024 · 0 comments · Fixed by #1472
Closed

Consistent wording for UI in asset groups: Dynamic asset filter or rule #1431

EllynBsc opened this issue Sep 13, 2024 · 0 comments · Fixed by #1472
Assignees
Labels
bug use for describing something not working as expected solved The issue has been solved tiny use to identify tiny feature to develop or bug to fix (< a week to solve)
Milestone

Comments

@EllynBsc
Copy link
Member

Problem

At the moment, we have 2 wording for the same thing: Dynamic asset filter or rule.

Screenshot 2024-09-13 165717
Screenshot 2024-09-13 170629

Solution

Change the dynamic asset filter for rule to have consistency. TBD

@EllynBsc EllynBsc added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team tiny use to identify tiny feature to develop or bug to fix (< a week to solve) and removed needs triage use to identify issue needing triage from Filigran Product team labels Sep 13, 2024
@EllynBsc EllynBsc added this to the Bugs backlog milestone Sep 13, 2024
@MarineLeM MarineLeM self-assigned this Sep 18, 2024
@MarineLeM MarineLeM linked a pull request Sep 18, 2024 that will close this issue
@MarineLeM MarineLeM added the solved The issue has been solved label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved The issue has been solved tiny use to identify tiny feature to develop or bug to fix (< a week to solve)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants