Hacker News new | past | comments | ask | show | jobs | submit login

For me none of the SaaS bug tracking systems are usable. They're all much worse than c. 1996 Bugzilla.



The only system that I appreciate is taiga. It's extremely opinionated and quite un-configurable.

What I like about it, is that it enforces workflows (either scrum, kanban or simply one-large-backlog) The Way They Were meant. So it solves a lot of bikeshedding and solves me & my team from trying to invent "something that works for us".

The idea proposed by OP works quite well there too, with kanban. Just pick the card at top, and never have more than one card per working person in "active" at any time.


Oh cool, didn't knew about it and it looks like it may be the sweet spot.


A quick web search gives me taiga.io, taiga.pm.

What's the diff if any?


I did not know about taiga.pm. I use the hosted version at taiga.io.

But, since Taiga is FLOSS[1], anyone can host it and/or build a business around it, which -I suspect- is what taiga.pm does.

[1] https://github.com/taigaio




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: