It would be nice if I could link two bugs that have a relation. Like linking issues in Jira. It would also be nice if a bug could have sub-tesks (or sub-bugs)

Hmm, not so sure about that. My understanding is that it's a feature that is almost exclusive to Jira, and thus barely used by the developer community at large. This particular feature is not covered in https://github.com/MichaelMure/git-bug/issues/30#issuecomment-450877360 unfortunately.

Maybe you could explain what it's useful for?

Not saying we shouldn't do it, but the benefit is not obvious, especially compared to other common feature (assignee, due date ...)

We use the linking feature a lot. Some things can be solved with sub-issues. But we also have cases where multiple departments are involved that each run their own Jira projects. With linking them together we can keep track of what is all involved.

Especially when we have recurring tasks, the link issue feature helps tracking down how it was done last time. Copying the task or just the text and adapting it saves a lot of time.

Essentially it boils down to the question if git-bug is just for tracking bugs, or how well it could also be used as a project management tool.

Those are good points.

My intuition on that is that those things are a higher level than "raw issue", that is, project management. And those things comes in a lot of different incompatible flavors, with a lot of strong opinions. A small project has completely different need than a big company, the same way a SRE team need different feature than a web team.

TBD, but maybe the best way would be to implement those things in optional packages/plugins so that each project could use the feature set they care about.

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

github-actions (github-actions) added label lifecycle/stale 1 year ago

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.

github-actions (github-actions) added label lifecycle/rotten 11 months ago

github-actions (github-actions) removed label lifecycle/stale 11 months ago

sudoforge removed label lifecycle/dormant 7 months ago