Differences between GitHub Projects and ZenHub
To integrate your Avion story map with GitHub, we require that you use either GitHub Projects or ZenHub. Both GitHub Projects and ZenHub allow you to manage your underlying GitHub issues in a Kanban view. This means that your issues are able to maintain a “state”, which is represented by a column. For instance: To do, Doing and Done. Avion uses these states to map to the workflow defined in the story map.
Features of GitHub Projects
GitHub Projects is free
Projects are created at the organization level and consume issues from many repos
Issues can have a “state”, which is dictated by the columns on a Kanban board
Boards can be filtered by various attributes, for easier planning
More information about GitHub Projects →
Features of ZenHub
ZenHub is free for open-source teams
Workspaces can be created an an organization level and consume issues from many repos
Issues can have a “state”, which is dictated by the columns on a Kanban board
Boards can be filtered by various attributes, for easier planning
ZenHub offers a whole range of additional types for higher-level planning, such as epics and release reports
More information about ZenHub →
Integration Differences Between GitHub Projects and ZenHub
There are a few subtle differences in your Avion integration depending on which tool you use to manage your GitHub issues.
With GitHub Projects you can:
Map Avion story states to GitHub Projects Kanban columns
Optionally map Avion sizes to labels
Optionally map Avion tags to labels
Optionally map Avion releases to labels (repo and org projects)
In classic projects:
Map Avion releases to milestones (repo projects only)
With ZenHub you can:
Optionally map Avion releases to labels
Map Avion story states to ZenHub Kanban columns
Optionally map Avion sizes to ZenHub estimates
Optionally map Avion tags to labels
Last updated
