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

Multiselect feature #336

Open
ddelpiano opened this issue Oct 23, 2024 · 0 comments
Open

Multiselect feature #336

ddelpiano opened this issue Oct 23, 2024 · 0 comments
Assignees

Comments

@ddelpiano
Copy link
Member

ddelpiano commented Oct 23, 2024

Acceptance criteria:

  • checkbox in the header to select all the record shown in the table
  • checkbox per record so that I can select them one by one.
  • summary of the number of records selected in the header
  • button to display the users list in a dropdown
    • only the users that can get these records reassigned should show up in the list (e.g. only triage operator should not be visible if I try to re-assign a bunch of connectivity statements).
    • In the dropdown have an helper text that indicates that the list of users available is based on their roles and permissions, so if someone is not there need to to talk to an admin.
  • subheader to allow to select all the record in the system that are matching the filters set / all the records available from the backend given the filters set.
  • Whenever the user change filter then the selection is lost and the user will have to select again.

We need additional design for:

  • selection and assignment of one or multiple tags to a list of sentences/statements.
  • State transition for multiple records selected
    • if records are in different state, for now, we disable this option and show a tooltip with a message that says 'records are not aligned to be transition all to a single state' (we can change this text later).
  • add a note for multiple records selected

Note for the design and acceptance criteria later:

  • when the state transition is triggered, the list displayed will shrink if some records are not matching the criteria of the filters anymore
  • the selection instead is retained, so if I remove the filters I will be shown again the selection I had before.
  • Action triggers needs to be mindful of what is selected AND what is matching the filters, example, if I select 40 records and I do a state transition, 35 succeed and 5 fails only 5 will remain in the list. By acceptance criteria above we want to preserve the selection IF the filters are removed, but when we trigger an action we need to consider selection and filters.

@stappan could you double check the requirements above and confirm acceptance criteria for this? Thanks

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

No branches or pull requests

2 participants