Comment by khimaros
6 hours ago
same question here. the other limitation i ran into immediately was only having two status types: open and closed
6 hours ago
same question here. the other limitation i ran into immediately was only having two status types: open and closed
It's really hard (impossible?) to define a feature set that work for everyone. Every bug tracker is a bit different, and if you want to have everything you end with Jira, which I'm not sure is actually solving a problem.
However, git-bug's data model is designed in a way that you can add more "operations" on an entity (say: assign a bug) without every client having to implement it. You can also add your own entity type (pr, kanban, ...) the same way. Clients will just ignore that extra data and support what they want. This open the possibility for addons and so on.
For this specific case of the bug states, I want to add a config entity to configure that. You'd start with a reasonable default (open/close) but you could tune it for the needs of your project.
that sounds great and looking toward to it. is there an issue i can subscribe to?
There is https://github.com/git-bug/git-bug/issues/63, but I have plenty to do before that.