Using the Kanban boards in GitLab (plus Wolftune check-in)


#1

tl;dr: use “To Do” and “Doing” with assignments in GitLab Board view to pick and show current and next tasks

I finally made sense more of how to use the Kanban Board feature in GitLab.

First, it’s not useful for ordering cards the way some of these things work.[1] The primary purpose is to actually track immediate work and goals.

So, here’s a link with a Board for issues assigned to me: https://git.snowdrift.coop/groups/sd/-/boards?scope=all&utf8=✓&state=opened&assignee_username=wolftune

  • The labels “To Do” and “Doing” are now group labels available in all projects.
  • The board is nothing more than a visualization of which issues have those labels or not with the ability to drag between boards as a method of changing labels.

Other board setups are possible that highlight other labels, but the point is to treat them as mutually exclusive labels. So, no issue should ever have “To Do” and “Doing” both. And adding those labels to an issue is tantamount to moving an issue to one of the boards.

Each team member can (and I encourage this) do a similar sorting of tasks assigned to them. Treat “To Do” as whatever you intend to do soon or next. Don’t mark too many issues that way… if we want, we could rename that tag “To Do Next” or similar, “To Do” is just GitLab’s default. Treat “Doing” as something already started, actively working on.

Thus, besides filtering down issues for yourself, this is a public accountability and activity report. The board filtered to me shows you what I’m up to and what I intend to focus on next (and what I’ve got in my backlog in the “Open” board or finished in the “Closed” board).

So, while there’s a lot that isn’t captured there, that link above is a bit of a check-in, status report for me. Cheers!


  1. We experimented with doing that for ordering priority of projects to reach out to, and that probably should be moved to a totally different system because having each of those as an issue clutters stuff for anyone with access to that special project. ↩︎


#2

Is there any way we can date issues or give a “priority” status to them?


#3

There are labels for low/medium/high/top priority.


#4

There’s also due-dates as something that can be marked, and we can use milestones to highlight sets of related tasks on track for a current larger project.