Feedback process

Our current feedback process goes somehow like this:

• User gives a feedback or creates a bug report through a UserVoice feedback widget in the Contriboard
• This creates a new ticket in the UserVoice service which can be interacted with in the admin panel
• Zapier takes the ticket, converts it to a Github issue with the chosen properties (label, milestone etc) and sends the issue to Github
• The issue goes to our feedback repository 'teamboard-feedback'

Zapier has a lot of options to choose. We can (and should) for example filter the tickets which will be sent to Github from the UserVoice. We can also assign different labels and milestones for the github issues here. Few concerns about the Zapier are that it's a third party service and the free version only has 80 actions per month. This is why we should filter which tickets we really want to go to Github and what which should stay in UserVoice.

Integrations

Flowdock integration

Contriboard feedback (UserVoice) is integrated with our team chat Flowdock. This integration enables more rapid actions with incoming feedback and makes feedback more transparent to all team members.