Receptive.io (discontinued) vs. Zenhub

Receptive is very effective for multiple internal teams/department of a single product who need to scale their product feedback management effectively. We've been leveraging it for one of our products and it was so successful, that we implemented it with a second product. The main issue we ran into situationally with that was managing 2+ modules (products) in Receptive; it was a bit more difficult to present Receptive to two different customer bases/users (we couldn't change the appearance) and slightly confusing to do within the app (lots of filtering needed). I have heard that support of multiple modules is something that Receptive will likely be working on in the near future, so that's good news.

Incentivized

If you have more than 2 developers this thing is basically a requirement within github to manage sprints if you use agile methodology. Why use a different website entirely when you can run your entire board right from github itself? I've tried other solutions but basing everything on github issues makes it so no duplicate work has to take place. If the UX quirks and mobile were fixed this would be 10/10 for me! If you're only one or two devs on a team it may be overkill to use, but if you're going to scale it's better to put the process in early.

Incentivized

• Captures feature requests from customers
• Organize feature requests
• Communicate progress updates to customers

Incentivized

• ZenHub has a lot of basic functionality, so that limits the complexity of the application
• The ability to provide user defined labels and customize pipelines provides flexibility
• The integration with GitHub provides a seamless process

Incentivized

• Filtering in general is not easy
• I would like to be able to create a leadership priority dashboard
• I would like to know easily when something has been linked to Jira

Incentivized

• Additional communication/collaboration inside the platform would be helpful
• Integration with additional systems like Slack would be a plus
• sometimes web pages load slowly, but for the most part things are alright

Incentivized

Once it's up and running it's easy to use. It needs a little consideration to get set up perfectly for your own needs, but that is the same for any feature-rich software.

Incentivized

I have not had a lot of contact with support, but when I do it's quick and accurate info.

Incentivized

Support is good, but quite honestly, I haven't needed any support since 2015. As I remember, I was required to open a ticket and had to wait a few days for resolution. I give it a rating of 8 because of the lag in getting a solid resolution, but it was resolved adequately.

Incentivized

We had UserVoice prior to Receptive but it was just too clunky and extensive for our needs. It was less about automation and still very manual work to process feedback. It also didn't provide collaboration levels that we needed for our internal teams to work together. ProdPad was a very clean tool but also didn't enable us to automate the process like Receptive does.

Incentivized

I have used Workfront in the past, which in my experience, is best with a traditional waterfall methodology, similar to Microsoft Project and the other more traditional project management software projects. ZenHub is truly designed around the agile methodology. Other products that claim they are agile oriented seem to just be adjusting and tweaking their traditional product to include a few agile features.

Incentivized

• We were managing these enhancements in our support ticketing system, using spreadsheets, and it was TERRIBLE. Being able to tell a user "Great idea! Submit it to Feedback!" has saved my support team hundreds of hours.
• We have reduced incoming support requests when the request is really an enhancement - the ability to have a "Suggest Features" widget in our software sends users straight to Feedback.
• Because we can make some fields required, we can cut down on the need to reach back out to our users for clarification.

Incentivized

• No official review done.
• Saves developer time knowing what needs to be done next.
• Saves leadership time to easily plan sprints and review work done.

Incentivized