rubyforgood / rubyforgood/casa
Fix Report a site issue form
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?
all
Description
At the bottom of every page when a user is logged the footer contains "report a site issue".
Currently the report a site issue goes to a typeform link, however, we lost the password (or something I'm not sure) and we can no longer get the responses from this form. We need to fix this.
- https://github.com/rubyforgood/casa/pull/5788
- https://github.com/rubyforgood/casa/pull/5813
- Change this Typeform submission to instead send to casa@rubyforgood.org. This will probably involve making a new paperform and updating where the "report a site issue" link points
- Improve the questions in the form as needed (maybe there is unneeded info that we are asking for, use your own judgement)
Notes
Typeform URL: https://form.typeform.com/to/iXY4BubB
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 on the QA site and inspect the footer's “report a site issue” link, then review the existing Typeform URL and the completed pull requests listed in the issue. Replace the unavailable submission path with a Paperform that sends reports to casa@rubyforgood.org, refine the questions as needed, and verify the footer link and submission flow from the available user views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100