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

[Spike] Implement system for user-end bug reporting #92

Open
rolsanmordua opened this issue Nov 26, 2018 · 8 comments
Open

[Spike] Implement system for user-end bug reporting #92

rolsanmordua opened this issue Nov 26, 2018 · 8 comments

Comments

@rolsanmordua
Copy link
Contributor

Alex's suggestion.

Explore possibilities for site visitors to report bugs they may encounter. Possibilities include:

  • More prominent bug reporting button?
  • Google form to submit issues?
@alex-bellon
Copy link
Contributor

Current idea: Google Form that is linked on website, and sends an email to webmaster account whenever anyone fills it out. Then manually transfer to a GitHub issue. Hope is to eventually automate the second part.

@ChiaHuaLu
Copy link
Contributor

We can probably put a link to it in the footer?

@alex-bellon
Copy link
Contributor

Found this awesome gist showing how to get from Google Form to GitHub issue. GitHub also provides a way to make issue templates, so we can incorporate that as well. Will look into this in the coming days.

@ChiaHuaLu
Copy link
Contributor

Do we want to have form auto fill a git issue or do it manually? With manual, we can filter out some things that the reporter have no idea whats going out and validate unreliable user input

@alex-bellon
Copy link
Contributor

I want to implement some block in the middle so we can approve/deny them before they are sent off to GitHub. But I want to automate as much as possible.

@alex-bellon
Copy link
Contributor

I made the Google Form. I was looking at IFTTT, and it has integrations for both Google Sheets and GitHub. We could set up one routine that emails the Webmaster email when there's a new response. We go in and check it, then use some trigger (mark the row as valid, whatever) to trigger a second routine that will make the GitHub issue.

@ChiaHuaLu
Copy link
Contributor

I thought sending email on form submit was a built in functionality. It isnt?

@alex-bellon
Copy link
Contributor

Made the IFTTT recipes. As of now, a new row in the sheet sends an email to the Webmaster with the issue title as the subject and the details as the email body. We can 'approve' it by adding the label 'Issues'. This triggers another recipe which makes a new issue. At the moment, I am having formatting issues going from email to GitHub issue.

@rolsanmordua rolsanmordua moved this from Spikes to In Progress in ACM Website (Winter 2018) Jan 21, 2019
@rolsanmordua rolsanmordua added this to In Progress in ACM Web (Spring 2019) Jan 24, 2019
@rolsanmordua rolsanmordua moved this from New to In progress in ACM Web (Summer 2019) May 6, 2019
@alex-bellon alex-bellon moved this from In progress to New in ACM Web (Summer 2019) May 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

3 participants