NOTICE:Makerlog v4 Beta is currently being developed. You can follow the progress by following Makerlog, and read the roadmap here.

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, Chat, ...)  - Custom solution? (Can you share some details maybe?)  - Nothing? (In this case: Why?)

Join the conversation

Sign in to post a reply and interact with thousands of makers.

6 replies

Loading replies...

Where makers learn, build, and grow in public.

© Nifty Development, LLC