Make an overview of the various bug-trackers

When designing git-bug it would be very useful to have an overview of the various bug-trackers that are out there. Here is a sample of questions that I have:

Actor

what properties (name, email, login, id, avatar ...) does the bug-tracker know about an actor ?
what is mandatory, what is optional ?

Bug's state

how do they model a state ? Is it an fixed set of state, or is it extensible? configurable ?
how do they model the transition between these states ?

missing features in git-bug

For instance, Github support reactions to messages with a set of emojis. What other bug-tracker support that ?
What other important features other bug-trackers have ? Is there a common ground ? Are they incompatible ?

With the attention git-bug got lately, hopefully we can collaborate and fill the blanks together in a shared spreadsheet.

Things in italics are missing features.

GitHub

Actor: name (not shown by default), username/login, email (not shown by default, but may be useful for associating the user with commits), avatar
State: Open/closed, locked/unlocked, optional lock reason, assignees (≤ 10)
Categorization: labels (name + description + color), milestone (1 per issue), projects (multiple, can place issues in different columns)

GitLab (docs)

Actor: name, username/login, email (not shown by default), avatar
State: open/closed, locked/unlocked, confidentiality, todo, assignee, time tracking, due date
Categorization: labels (name + description + color), milestone, weight (0–∞)

Missing features

Potentially useful

An avatar might be useful, although we could also use Gravatar instead. However, not everyone has a Gravatar account.
Assignees would be useful.
Label colors would be useful for categorization (example), but it would be OK if they weren’t colored.
Milestones would be useful.
Due dates could be useful, but the same pitfalls affect them as timestamps.

Probably not useful

A username/login is useful for websites where people get notified when @mentioned and need to actually log in, but neither of those things happen here.
Issue locking wouldn’t be useful since anyone could unlock the issue, and the issue tracker isn’t publicly writeable so it would rarely be necessary.
Projects are overkill.
Confidentiality wouldn’t be useful since everyone can access the backing data.
Personal to-do lists aren’t helpful in a shared repository.
We don’t need time tracking.
I’ve never wished GitHub had weights.

@j-f1

@j-f1 thank you !

I started a shared spreadsheet, could you move over there ? https://framacalc.org/bugtracker

Sorry you are way too fast ;)

Also we should stay with facts only for now imho, we will decide from that what feature we can and should support, and how.

Maybe also have a look at https://dist-bugs.branchable.com/software/ (in theory, this link should have reached you already via various channels)

@neithernut

@neithernut yes thanks I saw it. We need the extracted data version to make educated decision on the design.

@neithernut

@neithernut maybe join the gitter channel ? https://gitter.im/the-git-bug/Lobby

Feel free to add new features/item as you see fit.

bugtracker.xlsx

Backup in case the online version get lost.

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

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.

Navigation Menu

Repository navigation

Make an overview of the various bug-trackers #30

Actor

Bug's state

missing features in git-bug

GitHub

GitLab (docs)

Missing features

Potentially useful

Probably not useful

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Make an overview of the various bug-trackers #30

Description

Actor

Bug's state

missing features in git-bug

Activity

j-f1 commented on Aug 22, 2018

GitHub

GitLab (docs)

Missing features

Potentially useful

Probably not useful

MichaelMure commented on Aug 22, 2018

MichaelMure commented on Aug 22, 2018

neithernut commented on Aug 22, 2018

MichaelMure commented on Aug 22, 2018

MichaelMure commented on Aug 22, 2018

MichaelMure commented on Aug 22, 2018

MichaelMure commented on Jan 2, 2019

github-actions commented on Jul 23, 2024

github-actions commented on Feb 4, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions