Welcome to Zenhub! Whether you have just created your very first Workspace or have been invited by a team member to join an existing Workspace, it's time to get familiar with the fundamental Zenhub Board features to ensure you hit the ground running!
Course Outline | |
| Skill | Complete |
| - Understand the benefits of the Board | ✅ |
| - View the Zenhub Board | ✅ |
| - Rename a Board pipeline | ✅ |
Instead of tickets or sticky notes, the Zenhub Board is made up of your existing GitHub data: issues and pull requests that exist within the repositories that make up the Workspace! With a Zenhub Workspace, you can connect multiple repositories together—even across GitHub organisations—to get a bird's-eye view into everything going on with your software projects.
The Board makes workflow visualisation simple and accessible in real-time, empowering you to track issues and projects from an idea, through triage, to planning, development, and further to being released.
Zenhub Pipelines
When viewing the Board, you will see a collection of pipelines that represent the stages that work goes through within your team.
When a Workspace is first created, the board comes with eight default pipelines as outlined below:
| Pipeline | Pipeline description |
| New Issues | Newly created issues land here automatically. |
| Icebox | Low priority issues that do not need to be addressed in the near future. |
| Product Backlog | Upcoming issues that have been reviewed, estimated and prioritised top-to-bottom. |
| Sprint Backlog | Issues ready to be worked on in the sprint, prioritised top to bottom. |
| In Progress | Issues currently being worked on by the team. |
| Review Q/A | Issues open to the team for review and testing. Usually this means the code is ready to be deployed, pending feedback. |
| Done | Issues that are tested and ready to be deployed to production. |
| Closed | Issues that are complete and closed land here. It is not possible to edit or delete the closed pipeline. |
While these default pipelines are a great starting point for any project, these can be customised and changed by you and your team to suit your particular workflow. Before making any changes to pipelines, we'd recommend discussing these changes with your team, working together and coming to a mutual agreement on pipeline names to suit your workflow.
Renaming and deleting pipelines
Now let's take a look at renaming one of your pipelines. To get started, double-click any pipeline name. From here, you will be able to rename the pipeline and save your new pipeline name.
You can also rename and delete pipelines by selecting the pipeline options cog next to the pipeline name. Why not check out our guide on customizing Board pipelines to make your board look and feel like home for your team.
Adding Pipeline Descriptions
Pipeline descriptions enable you and your team to effectively communicate what each pipeline means on the board. Adding a description to each pipeline ensures you can communicate what your particular workflow means within your workspace. Why not spark discussion with team members on what pipeline descriptions should be added to your board?
Now, let's take a look at adding descriptions to your pipelines.
Select the pipeline options menu where you can add a description for your pipeline:
