You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement a project board, to have a better overview of which Issues are currently worked on or which ones still need to be resolved. The board will have multiple columns, where each columns represents the current state of an Issue.
An Issue will always be only in one columns and may be draged from one column to another to alter it's state.
E.g.
The columns of the board may be implemented with labels. Then a column represents a query for all Issues with the specific label.
E.g. The [WIP] column would list all Issues with the assigned label WIP.
NOTE: As an Issue can only be in one column at a time, it must be ensured that the Issue never has labels assigned which are also other columns in the board.
Kanban are indeed a common feature of bug tracker. Obviously this will need to be be supported in git-bug's core, possibly with its own data-structure.
Activity
GlancingMind commentedon Apr 21, 2021
Upstream link to the mentioned and related milestone issue: #639
nippo commentedon Jul 16, 2021
👍
MichaelMure commentedon Nov 20, 2022
This is being worked on in #843
github-actions commentedon Jul 23, 2024
This bot triages untriaged issues and PRs according to the following rules:
lifecycle/stalelabel is appliedlifecycle/stalewas applied, the issue is closedTo remove the stale status, you can:
lifecycle/stalelabelsparr commentedon Oct 4, 2024
I understand why a bug could have just one status and thus appear in only one status-based column.
If, however, you base a column view on labels, why would you forbid a bug from having multiple labels?
I believe that Trello allows both of these paradigms.
github-actions commentedon Apr 2, 2025
This bot triages issues in order to help the maintainers identify what
needs attention, according to the following lifecycle rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedThis bot will not automatically close stale issues.
To remove the stale status, you can:
To avoid automatic lifecycle management of this issue, add
lifecycle/frozen.