GitLab has powerful and flexible kanban boards (which we call issue boards) to help teams prioritize, manage, and track work execution. They are geared towards software development teams, but are also flexible enough for other teams in your organization to manage any type of tasks requiring tracking.
Issue boards are intended for planning sprints, tracking execution during sprints, and even evaluation after the fact, including integrating with value stream management with custom workflows and burndown/up charts.
GitLab issue boards have evolved beyond just allowing teams to track Agile workflows. You can also use them for sprint planning, cross-functional planning, and even user assignment visibility. Since we already have three types of lists in GitLab (labels, milestones, and assignees), users/customers have been finding new ways to use issue boards. We have to be careful as we evolve issue boards in the future that we don't let this immense flexibility create too much complications that hinders users from easily using issue boards. At the same time, we want to still retain that level of power so that users can do planning the way they want. Below are some ways we are considering to further refine the design. But in general, our vision of issue boards is to allow teams to organize and track their work in most flexible part of GitLab.
We are now focused on helping users better use the existing powerful capabilities of issue boards. In particular, we are improving the design of issue boards with more opinionated workflows. We are also integrating epics into issue boards.
The top competitor in this space is Atlassian's Jira, who are entrenched in many enterprise organizations who need an Agile/Kanban board solution. Atlassian also bought Trello, which is another significant player in this space, which has emphasized usability and being able to abstract out underlying software implementation details of an Agile sprint, to just simple task planning with a board interface.
Jira's and Trello's boards have inspired us to further refine and make our boards even more usable. In particular, we have the following ideas sketched and scoped out, including doing a lot more right in the board itself, without leaving it:
Similar to Project Management, the analyst landscape is focused on enteprise agile planning and value stream management. Kanban boards are a means to further make these processes more refined and efficient. See:
Customers really want a way to do workflows inside GitLab. They see the opportunity with label lists, but feel the pain of the shortcomings. So that's why Group board with custom workflow is so crucial to achieve this.
Users in general want custom workflows that work, with no pain, and weird behavior. They really want first class workflow states integrated into boards. So Group board with custom workflow and Custom workflow per group need to be achieved to satisfy that.
GitLab team-members want more flexibility to do even more with boards. In particular, GitLab team-members really want to take advantage of epics integrated in boards. Epic swimlanes are thus crucial here.
The most important items are further refining the board with more opinionated designs, adding swimlanes, and allowing users to do more without leaving the board itself.