Projects (beta): Group by on Kanban board to add swimlanes #5654
-
I expected the group by function to add swimlanes to the kanban board view. There are many use cases for adding swimlanes to a kanban board, the most common is having an expedited swimlane for critical bugs or other urgent work. I could see other uses at the project level to create swim lanes by repositories or by custom fields to allow work to be organized by the team that is executing said work. All the items in the swimlane would be used by that team. There are many use cases: Here are some examples of kanban swimlanes. To keep it simple I am linking to a microsoft version of swimlane docs, but it is a pretty standard feature of a lot of kanban boards. https://docs.microsoft.com/en-us/azure/devops/boards/boards/expedite-work?view=azure-devops |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 4 replies
-
I would also like swimlanes on boards. Group by could provide that. I wonder if it shouldn't carry over across views. |
Beta Was this translation helpful? Give feedback.
-
I'd like to use this kind of grouping to create one column per release cycle, to share a "roadmap" view with users. |
Beta Was this translation helpful? Give feedback.
-
We use the same feature in JIRA. Even when we are working on the smallest task in an AgileProject, we can see which Story we are working on. Are we in a hurry to start the next Story? We need Kanban + Swimlane to know if the team is working on the next Story in a hurry. The Swimlane puts the SubTask in a box. This is much easier to recognize than a Label. When the box is empty, the team can start working on the next Story. This is a very simple rule. We are looking forward to your implementation. |
Beta Was this translation helpful? Give feedback.
-
A "Grid" layout for views would be the logical offspring of "Table" (i.e. rows) and "Board" (i.e. columns) layouts. |
Beta Was this translation helpful? Give feedback.
-
Swimlane support would definitely be helpful and make it so that we can migrate our full workflow over to GitHub Projects, without much variation in terms of our current workflow, but makes it a friendlier Dev experience for our dev teams. |
Beta Was this translation helpful? Give feedback.
-
I just got on the waitlist for the Tasklists beta. Anyone here testing already? I imagine with the "tracked-by" filter you would have something closer to utility of swimlanes, albeit restricted to tracking relationships so not very general. |
Beta Was this translation helpful? Give feedback.
-
thanks for mentioning that I haven't seen the Tasklists yet
…On Thu, Feb 2, 2023 at 5:06 PM Ian Carroll ***@***.***> wrote:
I just got on the waitlist for the Tasklists
<https://github.com/features/issues/signup> beta. Anyone here testing
already? I imagine with the "tracked-by" filter you would have something
closer to utility of swimlanes, albeit restricted to tracking relationships
so not very general.
—
Reply to this email directly, view it on GitHub
<#5654 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA4ABCDLVBIOMPTI52N6PLWVQ4YNANCNFSM5EBNYJEQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
👋 This is coming! Check out the roadmap issue for more details, and note that this will land early Q3 (July-Sept), rather than Q2 (April-June) as noted ✨ |
Beta Was this translation helpful? Give feedback.
-
This is deployed and in the product.. closing discussion. |
Beta Was this translation helpful? Give feedback.
👋 This is coming! Check out the roadmap issue for more details, and note that this will land early Q3 (July-Sept), rather than Q2 (April-June) as noted ✨