ZenHub

The only solution for teams that depend on GitHub

Kommentare: We started using it in our dev teams (most of the company), but it worked so well, that we extended its use to Marketing, Finance and HR. We even created empty repos in GitHub, so that those teams can have their own boards. The cost is reasonable and we ended up with a powerful collaboration tool on shared artifacts (GitHub) and a basic, but sufficient task/project management tool (ZenHub). We even cancelled our Aha! Subscription, because we had simple product needs and the Roadmap feature, in combination with epics was enough for us.

Vorteile:

Ingenious way to bypass the issue of GitHub's poor API and data model, that makes it practically impossible for any integration to offer true value, with minimal overhead. It has just enough features to make our life easy, with minimal overhead.

Nachteile:

Sometimes (rarely) updates may get lost, when done via ZenHub. You do need to open the GitHub project occasionally, as you don't have exactly the same ability to modify issues and milestones from within ZenHub.

Nice connection to github

Kommentare: We use ZenHub to represent our backlog and workflow. It has epics and individual issues on the board.

Vorteile:

It has the same product management column set up that most PM tools have. One advantage I've seen over other PM softwares is that you can put epics in other epics. This allows you to put multiple epics into one epic to represent a bigger piece of work.

Nachteile:

I don't like that it's limited to kanban. You can't have different boards for teams within your repo (or I haven't figured out how) so you're all working off the same board. There aren't specific boards for sprints so you could set up columns to represent your sprint but it's not as easy as something like Jira.

ZenHub: the successful GitHub Project Management Plugin

Kommentare: Very good addition to the great GitHub CVS

Vorteile:

The project scheduling and management features are very advanced and sometimes surpassing leading project management software on the market. It is compatible with GitHub and hence is oriented towards software projects. The enterprise version provides a rich collection of collaborative tools for developers which adds to those available in GitHub. Tasks can be created and maintained very flexibly with very intuitive GUI interaction. Being the project management missing part in GitHub, ZenHub is a perfect synergy for collaborative project management for large scale software projects. Tracking software issues and bugs is very facilitated as well. But again we rely on GitHub to do such management tasks.

Nachteile:

The price is a bit high for large scale projects. A more flexible licensing strategy could be more appealing. Some GUI bugs show here and there but the developers are very actively responding to bug reports.

Easiest to use for scrum/kanban

Vorteile:

This has been a tank in my project management arsenal. The simplicity and integrations available with Zenhub are amazing. It's easy to catch on and integrate with the team. U can have multiple boards and have tickets sync across multiple boards based on how you have programmed it. I use this as the first option for any new project I take on. U can set up feature tickets or bug tickets from the support board to automatically go into dev boards and sync with the product road map board. The programmability is amazing and it generates the perfect reports as needed as well as the simplicity and ease of use makes it my first choice.

Nachteile:

I have nothing to say but good words about zenhub.

A rich layer ontop of GitHub issues

Kommentare: My experience with ZenHub was great, I have tried other tools to see if they could do better, but stayed with ZenHub in the end.

Vorteile:

Integration with GitHub is awesome. Kanban works great and both Epics and Stories are very well developed features. It has all one could expect from a tool to manage tickets in an agile fashion.

Nachteile:

The UI is sometimes not ideal, for example you might click out of a sidebar/modal thinking it saved your changes but it doesn't. Once you get used to it it's not a major issue, but comes back at every estimate session.