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
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.
maybe zoe's r4g account can? Or maybe we can get Zoe to break back in for us?
Change this typeform submission to instead send to casa@rubyforgood.org. This will probably involve make 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)
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.
The text was updated successfully, but these errors were encountered:
its still open but its more of an internal issue. We need to evaluate if typeform is the best way to do this or not. That's what the "core team" label was meant to represent.
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.
Notes
old typeform: https://form.typeform.com/to/iXY4BubB
How to access the QA site
Login Details:
Link to QA site
Login Emails:
/all_casa_admins/sign_in
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.
The text was updated successfully, but these errors were encountered: