3 ms·
Whenever one of these discussions starts, it's usually about 50% of the complainers saying "I don't specifically like JIRA" and 50% saying "This isn't about JIR
by ryandrake 8y ago
Whenever one of these discussions starts, it's usually about 50% of the complainers saying "I don't specifically like JIRA" and 50% saying "This isn't about JIRA--I don't like the idea of using any kind of ticketing system to plan, track, and execute projects".
The first argument is fine. Personal preference. You might have a different one you like best. I've used close to a dozen issue trackers, and to me JIRA is pretty much middle of the road. Not great, not cancer. It does a job, and is kind of a pain to configure. But to argue against the very idea of tracking bugs and features in a database? That's kind of bonkers unless you're a one-person development team and also double as the product owner, UI designer, and QA tester, and you don't have managers or other stakeholders who want to be able to know how far along the project is.
When your team size is >1 and you have more than a single day of work to do on the project, you need some kind of tool to organize and coordinate planning, design, development and testing activities. What are you going to use? Excel? Handwritten notes? I'd love to hear from developers who successfully finished a team development project without a bug tracker. At the risk of staking out a provocative position: I don't think it's even possible.