3 ms·

Good luck! One thing you might want to highlight is all the developer time that's wasted searching for things (or how to do things) in JIRA. It causes frustrat

by atonse 8y ago

Good luck! One thing you might want to highlight is all the developer time that's wasted searching for things (or how to do things) in JIRA. It causes frustration and is a true waste of time. But again, I don't think there's one issue tracker to rule them all. Gitlab's appeal was less about it being way better, and more about it being fully integrated.

beatgammit 8y ago
> I don't think there's one issue tracker to rule them all Oh, definitely. GitHub and GitLab issues are both pretty nice. However, they're not meant to be super featureful, and I think there's a niche between those types of issue trackers and Jira, where most people are actually probably better served by something simpler than Jira. Some very large projects are managed with GitHub/GitLab issues, so there's definitely an advantage there, but they don't work when you want to track other things with them (e.g. hardware design/release process, customer support tickets, etc). I just need to figure out what people dislike about Jira, then match the most common use cases making Jira's weaknesses my advantages. However, I'm not fully invested in it yet, but we'll see how much I get fed up with Jira/Gitlab issues (I work on projects that use both).