Swim Lane Mode (aka Kanban)
Categories
(bugzilla.mozilla.org :: Bug Creation/Editing, enhancement)
Tracking
()
People
(Reporter: emceeaich, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(2 files)
You're looking at a bug list and quickly want to assign bugs into groups.
Those groups might be:
- Priority
- Milestones (represented as tracking flags)
- Release statuses
When viewing a bug list allow entry into a mode that allows a user to select criteria from the common attributes of the bugs (priority, type) as well as the shared flags among the bugs.
Once a criterion has been selected (optionally restricted to a set of values) create a set of boxes (see attachment) which become drop targets for the list of bugs.
Reporter | ||
Comment 1•6 years ago
|
||
Reporter | ||
Comment 2•6 years ago
|
||
See also GitHub's project mode
Comment 3•6 years ago
|
||
This probably depends on Bug 1527385. If everyone can create project boards, it will be chaos. Or, if only admins or triage owners can create boards, it will be useless.
See also: Project board permissions for an organization on GitHub
Comment 4•6 years ago
•
|
||
It’s not difficult to implement the Kanban view if it’s just a different UI of bug lists. We can do it with the existing REST API and no backend change is needed, just like what Bz Kanban Board does.
3 possible views of bug lists:
- Grid View (Bugzilla’s current bug list UI)
- List View (like GitHub issues)
- Column View (based on a specific field like Status, Priority or Milestone, as Emma mentioned in Comment 0)
But that’s probably not what’s expected of Kanban boards in general. There are many more things to consider:
- multiple project boards
- membership: who can see & edit
- custom columns: different from bug statuses
- custom labels/keywords
- manual card sorting
- multiple assignees per card
- real-time updates
The Column View of bug lists and Kanban boards may look similar but are different :-)
Maybe we can start with the former and later work on the latter.
Comment 5•6 years ago
|
||
See also: https://github.com/bayoteers/AgileTools
Not quite what this bug is talking about - it's more scrum management than kanban - but it's certainly related.
You can set up multiple teams, and within each team, multiple backlogs and a single sprint. Bugs can be placed in a backlog or moved into the current sprint.
Supports drag-and-drop ordering within pools, and provides useful burndown charts.
I don't know to what extent, if any, this kind of functionality overlaps with what is being considered here, but thought I'd bring it to everyone's attention.
Comment 6•6 years ago
|
||
(PS - I have no affiliation with AgileTools, but we use it heavily and I have submitted a few patches.)
Description
•