Collecting Feedback on Behalf of a User

When it comes to collecting feedback from your clients or your team, knowing who reported the feedback is crucial. Understanding how the user is using the product helps to resolve issues and create features as quick as possible.

With Bugflow, we go a step further. Not only will you see who reported the issue within Bugflow, but also in the destination tool where your project is being managed.

Use Case: Collecting Quality QA Feedback with Jira

Let’s say you have a QA team that uses Jira to manage feedback and Bugflow to report feedback. A member of your QA team reports feedback through Bugflow, but your team wants to manage the feedback within Jira. You don’t want to cross-reference who reported what, set up duplicate email systems and get a ton of noise in your inbox.

With Bugflow’s identity connection, you are able to see who reported the issue without cross referencing Bugflow and without receiving duplicate emails. The issue comes into Jira from the user account who reported it, keeping your workflow in-tact and quickly collecting feedback.

Use Case: Development Team on GitHub

Working on a development team, having the issue get created from the user who reported it, streamlines communication, helping you solve issues with ease while keeping you in the workflow you are used to.

Within our small team at ServerSideUp, Jay uses Bugflow to do QA rounds on our apps, while I fix the bugs. When he reports an issue, and it comes in from him, I can respond right in GitHub to the issue and he will be notified.

All communication is in one centralized location. Using Bugflow to collect high quality feedback and organizing the issue into an actionable item, allows a development team to operate seamlessly and get the answers they need right away.

Behind the Scenes: How do our integrations get the right user?

Identity management is crucial to making Bugflow operate and is the base for all current and upcoming features (automated reports, feature request boards, etc.). Behind the scenes we built an identity management platform using SaloonPHP and Laravel.

By structuring our system correctly, we are able to quickly bind third-party integration identities. These identities are bound through an OAuth 2 connection, and stored securely in our database.

When feedback is reported, we quickly persist the data so we can use it within Bugflow and process it through the desired automation. From there, we create a queued task. The actual sending to the destination takes some time since it’s a third party and often multiple steps are involved.

The queue will receive a feedback record, see that it was reported by the user and it’s destination. It will look up the identity for that user on the destination. All third-party integrations provide some sort of user ID when you connect through OAuth. We then, fill that in on the request to the third-party integration and voila! The user who reported the feedback is mapped to the user on the third-party!

Check out the diagram below for a visual on how this works.

Of course, if you have any questions or want further information before choosing to switch your project or agency to Bugflow, feel free to reach out to [email protected]. We’d love to help!