|
Those all seem like valid points. Especially about $$. I am wondering if JIRA can't handle the equivalent of a monorepo, with one giant project. Was that the situation? Also, I don't intend to defend JIRA from a cost or infrastructure perspective, just as a tool. If you are shopping around for a ticketing system might I offer this generic minimum spec sheet:
* Items should all have a unique identifier that can be used in the developers workflow
* Any item should be able to be a sub-item of another item.
* It should be fast enough to not waste development time (time spent in tool). If your ticketing/work/bug system doesn't allow those (and I believe GitHub issues might not), then you are doing your team a disservice. The reason I usually turn to JIRA, is that somehow it manages to be everything to everyone. I was managing a small team at a startup, and the developers only looked at the detail view and the kanban view. Almost any "update" to JIRA happened via including a ticket number in a git commit, branch, etc. However, the QA team, had some crazy pipeline that happened after the engineers deemed it done, and those two workflows didn't affect each other, and worked seamlessly. Product, had an entirely different workflow before engineers even saw a ticket. Then after grooming, and sprint planning, the team set a goal of how which tickets would be done and in what order. Engineers would go back to their desk, and just use JIRA for viewing the details and commenting on things usually for product/design. Also, if I wanted to cut a release of something (at the time we did weekly deploys, even though master was always considered deployable at any time), and I could click a button in JIRA to make a release that automatically knew what had changed from git. All of those tickets got updated to `released` automatically from the deploy. You may not need JIRA. But a lot of engineers have put a lot of hours into a marvel of software that does way too many things. Its an amazing tool. But you may not need a multi-tool such as JIRA. You might just need a hammer. (Lastly out of curiosity, have you contacted their support about optimizing your performance? I am curious before I choose self-hosting in the future.) |