rubyforgood / rubyforgood/casa
Volunteer table
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
What type(s) of user does this feature affect?
- supervisors?
- admins?
- all casa admins?
Description
The volunteer table is crowded and has a combination of volunteer and case based information. This issue requested an emancipation button to be added as well. To accommodate that the case based portion of the table can be broken out into a dropdown.
Some outstanding questions to determine if this is the correct solution:
- what are the most heavily used pages and is there a different solution already in progress
- what are common actions taken on the volunteers page
Best case improvements:
- change case numbers(s) to # (of total cases)
- shorten email with ellipsis (add tooltip, ~12 character, copy button)
- carets up when open, right facing when open
- expand/collapse at the top of the table
- scroll when there are a lot of cases
Screenshots of current behavior, if any
Potential solution to table overcrowding + clarification of case level vs volunteer level information
How to access the QA site
Login Details:
Link to QA site
Login Emails:
- volunteer1@example.com view site as a volunteer
- supervisor1@example.com view site as a supervisor
- casa_admin1@example.com view site as an admin
- all_casa_admin1@example.com view site as an all casa admin
- go to
/all_casa_admins/sign_in
- go to
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the QA site's volunteer table and compare the volunteer, supervisor, CASA admin, and all-CASA-admin views using the provided sign-in paths. Resolve which pages and actions need improvement with project stakeholders, then implement the agreed table behavior and verify the resulting layout and interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100