ZenHub

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

Vantaggi: 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.

Inconvenienti: 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.

Vantaggi: I love how this software takes an existing feature (i.e. GitHub issue) and literally supercharges it, giving it new scope and meaning. It lets you organize work in a fast, reliable and effective way with teams of any sizes. I’ve been using it with a small team of web developers and it really changed for the better the way we plan our sprints and how well we communicate progress to other stakeholders.

Inconvenienti: The learning curve might seem a bit steep, you need to become familiar with how GitHub features like issues and labels map to concepts like milestones and epics, but once you get the gist of it you are going to love this software.

Commenti: We're using ZenHub to organize and manage the code development inside of GitHub. We use Chrome / FireFox plugins to add the ZenHub layer directly into GitHub.

Vantaggi: 1. It works seamlessly on of the original GitHub site (via the Chrome / FireFox plugin).
2. It provides the detailed guide not only on how to use the tools but on how to manage agile projects in general.
3. It provides a really slick and well-thought interface and usability experience.

Inconvenienti: There are some details that I wish would be improved:
1. I wish that sub-issues of an Epic could be ordered (when planning viewing them in the proper order is important).
2. I miss the ability to add automated actions, like:
2.1. Move issue to a certain pipeline when a code review is requested
2.2. Move issue to a certain pipeline when a code review is approved
2.3. Switch issue to a certain assignee when moved to a pipeline
4. ZenHub provides the "Done" pipeline, but the issues there are not actually counted as "done" in the reports.
3. Now ZenHub allows viewing issues as a pop-up in the pipelines. I wish the same experience would be available from the Epic planning board.

Vantaggi: The code of my team lives in github so therefore, so do my developers. We used JIRA for change and defect management but developers found it tedious. Not so with github.

Inconvenienti: The UI has some inconsistencies that annoy me:
* Text fields do not store their value unless you press update, but things like dropdowns update as soon as you release the mouse. It makes me uncertain: did this particular change take or not.
* The close button puts the ticket in the closed state (in addition to closing the window) but does not pop up a message that it basically says we're done, nor asks to specify anything. Especially in the beginning, this made it far too easy to remove tickets from the board by mistake.

Vantaggi: Zenhub is integrated with Github and thus enable me access this program with my Github login. It also provides me with an intuitive layout to monitor the progress of projects I manage.
I have also skipped using Jira and depended fully on Zenhub to delegate tasks to my team members at work ,and for disaster recovery management.

Inconvenienti: Zenhub's user interface is very much clumsy and takes time to get used to. It also renders my Github page unusable ,while it is active.