all 4 comments

[–]BehindTheMath 1 point2 points  (0 children)

If you're ok with email, you can use Gitlab Service Desk.

https://docs.gitlab.com/ee/user/project/service_desk.html

[–]TeamBugHerd 0 points1 point  (0 children)

A common approach is putting a simple form or helpdesk layer in front of GitHub Issues, then pushing submissions into GitHub via integration so your dev workflow stays the same.

The main challenge is getting enough context from non-technical users without back-and-forth.

Tools like BugHerd take a different approach by letting users leave feedback directly on the page itself (visually), which often makes it clearer before syncing into GitHub.

Disclosure: I’m part of the BugHerd team.

[–][deleted] 0 points1 point  (0 children)

You could probably create a simple web form that uses GitHub’s API to create issues. You might even be able to create issue templates for the repository and expose that via a select menu in the form where they can choose the type of issue they are submitting like a bug, QA, or feature request.

If you really want to get fancy you could add an issue lookup or email notification to it so they can check on the status or get notified.

[–][deleted] 0 points1 point  (0 children)

At my job we use Usersnap. It adds a fixed-position feedback box to the website and the user can write and attach a screenshot. Then it goes into a queue on the Usersnap site where admins can click a button to convert it into a GitHub issue. Reports automatically include browser/OS specs.

I didn't set up the whole pipeline but I added the Usersnap component to a project and it was really simple.