You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently only default styling on select all and clear all affordances at the top of lists. We should define what is should be. Some thoughts are:
Should they maybe not look like buttons at all (checkbox and styled "clear all" instead?) or should we come up with a special button style for these that have clearer meaning?
Should "clear all" show at all before multiple are selected? Or what good styling can we provide for a disabled state? (A disabled state it does help the user discover multiselect capability)
Below to be filled out by UX during kickoff Q&A to the best of current understanding
Size
Effort level (xs, sm, m, lg, xl) XS
Scope
What will we do? What will we NOT do?
User needs statement(s)
As a [type of user], I need/want to [action(s)], so that I can [goal].
Description
There is currently only default styling on select all and clear all affordances at the top of lists. We should define what is should be. Some thoughts are:
Below to be filled out by UX during kickoff Q&A to the best of current understanding
Size
Effort level (xs, sm, m, lg, xl)
XS
Scope
What will we do? What will we NOT do?
User needs statement(s)
As a [type of user], I need/want to [action(s)], so that I can [goal].
Additional notes
Knowns/unknowns, stakeholders, time/dependency considerations, deliverables
Examples in current UI:
The text was updated successfully, but these errors were encountered: