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

Feedback mechanism #3840

Open
sstrubberg opened this issue Dec 7, 2023 · 2 comments
Open

Feedback mechanism #3840

sstrubberg opened this issue Dec 7, 2023 · 2 comments

Comments

@sstrubberg
Copy link
Member

sstrubberg commented Dec 7, 2023

image

This part of our website is tied to an Alchemer survey. People submit feedback and then it gets dumped into survey via the Alchemer API.

The problem

  • The API key hasn't been working since 05/2022 😩
  • Alchemer access at IBM is being sunset in favor of Qualtrics.

The solution

  • Get access to Monday's API and tie this form to it, along with some sort of notification in Slack when someone hits it.
  • We also need to know when/if this thing ever fails.
  • When a user submits the entry should record the following:
    • The positive, negative, or neutral experience
    • Any comments
    • The page they were on, including tab.
    • The time/date when they submitted.

Support

https://ibm.monday.com/apps/manage?placement=dev_center

@github-project-automation github-project-automation bot moved this to Triage in Roadmap Dec 7, 2023
@sstrubberg sstrubberg moved this from Triage to Later in Roadmap Jan 8, 2024
@sstrubberg sstrubberg added this to the 2024 Q1 milestone Jan 8, 2024
@sstrubberg sstrubberg moved this from Later to Next in Roadmap Jan 8, 2024
@tay1orjones
Copy link
Member

A few alternative ideas:

  • Have the form submit a GitHub issue to a private repo
  • Have the form submit directly to a private slack channel
  • Have the form submit to an Airtable

I'm not sure if Alchemer/Qualtrics provides reporting, PII shielding, or whatever else, but some of these ideas would allow quasai-reporting (GitHub issue labels for positive/neutral/negative, etc). We could also update the form to say "your responses will be public".

@laurenmrice laurenmrice modified the milestones: 2024 Q1, 2024 Q2 Mar 27, 2024
@sstrubberg sstrubberg removed this from the 2024 Q2 milestone Jun 26, 2024
@sstrubberg sstrubberg moved this from Next to Icebox in Roadmap Jun 26, 2024
@sstrubberg sstrubberg moved this from Later 🧊 to Next ➡ in Roadmap Dec 10, 2024
@sstrubberg sstrubberg moved this to 🪆 Needs Refined in Design System Dec 10, 2024
@sstrubberg sstrubberg added this to the 2025 Q1 milestone Dec 10, 2024
@mattrosno
Copy link
Member

If I remember correctly, the form from this website sent a request to the serverless function from the Vercel-hosted site? If not using Vercel hosting, would we need to spin up an IBM Cloud serverless function to keep secrets private or can Gatsby do this now?

Even though this doesn't appear like PI to me, when re-adding this, let's consult our legal counsel to add a privacy statement if necessary. Maybe it would be something like:

Do not include Confidential information in your responses or any names or other Personal Information (PI) or Sensitive Personal Information (SPI) that could identify another person. Comments will be reviewed and potentially shared as written and will not be edited.

Or maybe it's as simple as adding a checkbox that says:

I have read and understood IBM Privacy Policy

Which links to: https://www.ibm.com/privacy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🪆 Needs Refined
Status: Next ➡
Development

No branches or pull requests

4 participants