-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Swimlanes on kanban boards #14670
Comments
Could you please elaborate a little what swimlanes are? |
@delvh Swimlanes in Jira: swimlanes: "expedite", "bugs", "everything else" Also from wikipedia: swimlanes: unlabeled one and "fast track / defect" |
👍 Thanks, now I know what you want included. |
Other nice examples for swimlanes are given by |
We also use swimlanes on assignee (in our old redmine) - so we can use it for standup - makes it easy to see what each has in their pipeline - to remember what to talk about in standup for each person :) |
As another data point for how swimlanes get used, I'm team lead on a multidisciplinary project (EEs, Firmware engineers, Software engineers, and more). We use swimlanes to separate out each of the skill sets. We keep them all on the same board as they're a single project with interlinking work. I know both Go and JS and am happy to help with the implementation if someone is looking for a hand. |
if someone who knows the project well - could outline HOW this should be approached - to allow for actual merging of it into the project.. I'll also gladly assist with some coding its very sad to work on this - to have it never merged.. and swimlanes is the biggest drawback of gitea over gitlab (or any other kanban tool) - for us |
This is actually a "first attempt" at implementing this AFAIK : #21963 |
Now that we have basic kanban functionality, there are many interesting areas to pursue.
I propose that the first should be swimlanes. It allows us to split major work into smaller parts.
Ultimately it would be nice to have the same functionality that ZenHub has, but we need to get there slowly, feature by feature.
The text was updated successfully, but these errors were encountered: