1
5 Comments

How do you collect bug details from users/clients?

"Feature X doesn't work. Please fix!". As makers/creators, you probably know this sentence, right? If you're lucky you get a screenshot, ... that shows nothing.

How do you get the details that you need in order to understand the issue and fix it (in case it is actually a bug)?

  • Tools for log management/analysis? (e.g. Loggly, ...)
  • Tools for contextual bug insights? (e.g. Instabug, ...)
  • Written communication? (e.g. eMail, GitHub issues, Jira, ...)
  • Custom solution?
  • Nothing? (In this case: Why?)
on May 4, 2021
  1. 1

    For analyzing end-user browsing environment you could use our tool - https://yourbrowser.is/

    You create a custom checker page and provide it's URL to the user. They open in and you receive a report on their browser, operating system, mobile device, etc.

    1. 1

      That's cool. Thanks for sharing. 👍

  2. 1

    For ruttl, I earlier had a quick submit issue button inside my project dashboard. However, now I have created a separate slack community where people join in and share issues or discuss new features for the product. It's been working out pretty well lately.

    1. 1

      Thanks. Good to know that even a simple slack button works. Do your users have/require a slack account then? And how do you collect contextual info (e.g. logs) in this case?

      1. 2

        I've got firebase integrated for the platform. That along with data studio is helping my developer maintain all the logs,etc.

        The users don't need slack account as a mandatory step. I've given them the option to join the community to make ruttl better, that's all. They seem to respond quite nicely as well to the idea of slack community.