index.md

stage: Plan
group: Project Management
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments

Tutorial: Set up issue boards for team hand-off

DETAILS: Tier: Premium, Ultimate Offering: SaaS, self-managed

This tutorial shows you how to set up issue boards and scoped labels for two teams that work on issues in sequence.

In this example, you'll create two issue boards for the UX and Frontend teams. Using the following steps, you can create issue boards and workflows for more sub-teams, like Backend or Quality Assurance. To learn how we use workflow labels at GitLab, see Product Development Flow.

To set up issue boards for multiple teams:

1. Create a group
2. Create a project
3. Create labels
4. Create team issue boards
5. Create issues for features

Before you begin

• If you're using an existing group for this tutorial, make sure you have at least the Reporter role for the group.
• If you're using an existing project for this tutorial, make sure you have at least the Reporter role for the project.

The goal workflow

After you set up everything, the two teams will be able to hand off issues from one board to another, for example, like this:

1. The project lead adds the Workflow::Ready for design and Frontend labels to a feature issue called Redesign user profile page.
2. A product designer on the UX team:

   1. Checks the Workflow::Ready for design list on the UX workflow board and decides to work on the profile page redesign.

      

   2. Assigns themselves to the Redesign user profile page issue.

   3. Drags the issue card to the Workflow::Design list. The previous workflow label is automatically removed.

   4. Creates the ✨new designs✨.

   5. Adds the designs to the issue.

   6. Drags the issue card to the Workflow::Ready for development list, which adds this label and removes any other Workflow:: label.

   7. Unassigns themselves from the issue.

3. A developer on the Frontend team:

   1. Checks the Workflow::Ready for development list on the Frontend workflow board and chooses an issue to work on.

      

   2. Assigns themselves to the Redesign user profile page issue.

   3. Drags the issue card to the Workflow::In development list. The previous workflow label is automatically removed.

   4. Adds the frontend code in a merge request.

   5. Adds the Workflow::Complete label.

Create a group

To prepare for when your project grows, start by creating a group. You use groups to manage one or more related projects at the same time. You add your users as members in the group, and assign them a role.

To create a group:

1. On the left sidebar, at the top, select Create new ({plus}) and New group.
2. Select Create group.
3. Complete the fields. Name your group Paperclip Software Factory.
4. Select Create group.

You've created an empty group. Next, you'll create a project that will store your issues and code.

Create a project

The main code development work happens in projects and their repositories. A project contains your code and pipelines, but also the issues that are used for planning your upcoming code changes.

To create a blank project: