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

default to all contact types for new cases #6187

Open
bcastillo32 opened this issue Jan 26, 2025 · 5 comments · May be fixed by #6215
Open

default to all contact types for new cases #6187

bcastillo32 opened this issue Jan 26, 2025 · 5 comments · May be fixed by #6215
Assignees

Comments

@bcastillo32
Copy link
Collaborator

What type(s) of user does this feature affect?

  • admins

Description

When admins create new cases, all contact types selected should be the default. Currently, the admin has to select them all one by one. Please also add a "Select/Unselect all" as the first list option in the dropdown. By default, the "Select/Unselect all" should be checked.

Image
  • log in as an admin
  • Navigate to cases in the left navbar
  • click "+ New Case"

How to access the QA site

Login Details:
Link to QA site

Login Emails:

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.

@bcastillo32 bcastillo32 added the Help Wanted This is a special label that enables github to showcase issues that want help label Jan 26, 2025
@alex-yi37
Copy link
Contributor

I can attempt this one!

@compwron
Copy link
Collaborator

go for it!

@github-actions github-actions bot removed the Help Wanted This is a special label that enables github to showcase issues that want help label Jan 31, 2025
@alex-yi37
Copy link
Contributor

I noticed this contact types dropdown also appears in the page for editing a case at /casa_cases/:case_id/edit. Should the select/unselect all checkbox also appear there and default to being checked initially?
Also, do you know what the most common usage might be for the checkbox? Would an admin want all contact type options checked when creating a case and might only uncheck a few options ultimately? Is it likely they'd want to uncheck all options to then select a few?

@compwron compwron linked a pull request Feb 7, 2025 that will close this issue
@compwron
Copy link
Collaborator

compwron commented Feb 7, 2025

I noticed this contact types dropdown also appears in the page for editing a case at /casa_cases/:case_id/edit. Should the select/unselect all checkbox also appear there and default to being checked initially? Also, do you know what the most common usage might be for the checkbox? Would an admin want all contact type options checked when creating a case and might only uncheck a few options ultimately? Is it likely they'd want to uncheck all options to then select a few?

@bcastillo32 what do you think?

@bcastillo32
Copy link
Collaborator Author

I noticed this contact types dropdown also appears in the page for editing a case at /casa_cases/:case_id/edit. Should the select/unselect all checkbox also appear there and default to being checked initially? Also, do you know what the most common usage might be for the checkbox? Would an admin want all contact type options checked when creating a case and might only uncheck a few options ultimately? Is it likely they'd want to uncheck all options to then select a few?

@bcastillo32 what do you think?

Sorry - I was out out town for the week so am just seeing this now

@alex-yi37 - to answer your question, yes you are correct. Admins have asked for a quick way to select/unselect all contact types when editing a case.

When creating a new case, the default should be all contact types are selected. It's more common to either leave them all checked or remove a few.

let me know if this answers your question :)

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

Successfully merging a pull request may close this issue.

3 participants