Make process painless
Allow handoffs between teams and contributors to become a seamless part of everyday processes with little to no human intervention.
Effortless, errorless
collaboration
Never forget to pass the baton
Give teams the full context of an issue
Automate processes in
GitHub
Connect technical and non-technical teams
Automate handoffs between scrum teams
Effortless, errorless collaboration
Never forget to pass the baton
Give teams the full context of an issue
Automate processes in GitHub
Connect technical and non-technical teams
Automate handoffs between scrum teams
What our customers are saying
“We now have a record of progress and discussion. ZenHub has made our workflow simple and organized.”
Why software teams love workflow automation
For developers
For product leaders
Explore other features
Boards
Reporting
Sprint planning
Roadmaps
Planning poker
Zenhub extension
Key terms and concepts to know
Kanban boards are a project management tool for recording and tracking tasks. The boards are divided into several “pipelines,” representing the task's status. Kanban boards are a common tool in agile project management.
Workflow automations in Zenhub connect work being done in one Kanban board to another. Automation allows one issue to move from one board’s pipeline to another when it’s ready to be worked on by a new collaborator.
“Pipelines,” on a Kanban (or Agile/Scrum) board, represent the status of the work being done. For example, “In review” may be a status.
“Issues” in agile project management are another word for smaller tasks or individual units of work. In Zenhub, issues best suited to developers are GitHub Issues and issues best suited to non-technical team members are Zenhub Issues.
A workspace is a place where one team hosts their work. Workspaces can consist of multiple GitHub repositories and can be connected to one another using Workflow automation.
Frequently asked questions
What is a Zenhub board?
Zenhub boards are where you manage your work. Zenhub boards allow you to see the status of various GitHub issues are they’re being worked on, move issues between pipelines and prioritize issues.
What triggers an automation?
In Zenhub, a change in the status of an Issue, which is when you move an issue from one pipeline on your Kanban board to another, is what triggers automation. For example, when an issue moves to the “Closed” pipeline in Board A, it will then be moved to the “In Design” pipeline in Board B.
How are workflows set up?
First – you’ll need more than one workspace to connect the two. You can set up workflows by heading to the “Workflows” section on the left-hand side of your Zenhub board. From here, you can select a “trigger” pipeline, this is the pipeline that will trigger the movement of an issue. You then can select a “destination” pipeline, which is the pipeline the issue will move to once it’s been triggered.
Need more help?
