Skip to content

Add project board support #637

Open
Open

Description

@GlancingMind

This is an upstreamed issue originating here: GlancingMind#20 (comment)

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.

[TODO]     [WIP]   [Requires Review]   [DONE]
Issue2     Issue1  Issue5              Issue4
Issue3                                 Issue6

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.

Activity

  1. GlancingMind commented on Apr 21, 2021

    @GlancingMind
    ContributorAuthor

    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.

    As for GlancingMind#11 maybe you could implement the graphQL API with a mock (without persistence) to experiment with that in the webUI. I've noticed https://github.com/nishantpainter/personal-kanban that could fit the bill quite nicely.

    Originally posted by @MichaelMure in GlancingMind#20 (comment)

    Upstream link to the mentioned and related milestone issue: #639

  2. nippo commented on Jul 16, 2021

    @nippo

    👍

  3. MichaelMure commented on Nov 20, 2022

    @MichaelMure
    Contributor

    This is being worked on in #843

  4. github-actions commented on Jul 23, 2024

    @github-actions

    This bot triages untriaged issues and PRs according to the following rules:

    • After 90 days of inactivity, the lifecycle/stale label is applied
    • After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

    To remove the stale status, you can:

    • Remove the lifecycle/stale label
    • Comment on this issue
  5. sparr commented on Oct 4, 2024

    @sparr
    Contributor

    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.

  6. github-actions commented on Apr 2, 2025

    @github-actions

    This bot triages issues in order to help the maintainers identify what
    needs attention, according to the following lifecycle rules:

    • After 90 days of inactivity, lifecycle/stale is applied
    • After 90 days of inactivity since lifecycle/stale was applied,
      lifecycle/rotten is applied

    This bot will not automatically close stale issues.

    To remove the stale status, you can:

    • Remove the stale label from this issue
    • Comment on this issue
    • Close this issue
    • Offer to help out with triaging

    To avoid automatic lifecycle management of this issue, add
    lifecycle/frozen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions