The two... archtypical complaints typically I hear levied against JIRA are typically:
1) It's sometimes a tool for managerial micromanagement, such as the extraction of unreasonably certain estimates as "promises", which can then be adjusted further down by your project managers, which can then be used to pressure devs into crunch or worse, instead of as a means of adjusting expectations.
2) It's an extremely complicated piece of software which you can (read: will) overcustomize into oblivion, confusion, and general busywork. Having grown over the years, it's various complications are also not consistent with each other, so some features don't really work well with others. The antithesis of KISS or YAGNI.
3) Project managers will still ask you about stuff instead of referring to JIRA. What's the point of sending time estimates into the void if they're going to swing by and disrupt your flow to hear those same estimates from you in person anyways?!
#1 gives people a (reasonable) emotional reason to hate JIRA, #2 gives people a (reasonable) rational reason to hate JIRA. #3 probably counts for both. I feel like I'm the weird one out not having come to hate JIRA in my social circles.
Project management is important, but JIRA is just a tool, not project management. Ultimately, that's a communication problem with your stakeholders and the people who get to call the shots. Email, slack, trello boards, even water-cooler chit chat can be better than an over-configured JIRA install in the right hands with the right managers. Get everyone on the same page in terms of tasks and priorities, manage expectations, track progress, avoid last minute surprises...
Something like a Trello board is sometimes popular with the "JIRA is overcomplicated" crowd. I use it for personal projects sometimes. It's OK. I'm OK with JIRA in the right hands too though. You don't have to tweak every single knob and settings. You can practice some self restraint and avoid it nerd sniping you, probably.
1) It's sometimes a tool for managerial micromanagement, such as the extraction of unreasonably certain estimates as "promises", which can then be adjusted further down by your project managers, which can then be used to pressure devs into crunch or worse, instead of as a means of adjusting expectations.
2) It's an extremely complicated piece of software which you can (read: will) overcustomize into oblivion, confusion, and general busywork. Having grown over the years, it's various complications are also not consistent with each other, so some features don't really work well with others. The antithesis of KISS or YAGNI.
3) Project managers will still ask you about stuff instead of referring to JIRA. What's the point of sending time estimates into the void if they're going to swing by and disrupt your flow to hear those same estimates from you in person anyways?!
#1 gives people a (reasonable) emotional reason to hate JIRA, #2 gives people a (reasonable) rational reason to hate JIRA. #3 probably counts for both. I feel like I'm the weird one out not having come to hate JIRA in my social circles.
Project management is important, but JIRA is just a tool, not project management. Ultimately, that's a communication problem with your stakeholders and the people who get to call the shots. Email, slack, trello boards, even water-cooler chit chat can be better than an over-configured JIRA install in the right hands with the right managers. Get everyone on the same page in terms of tasks and priorities, manage expectations, track progress, avoid last minute surprises...
Something like a Trello board is sometimes popular with the "JIRA is overcomplicated" crowd. I use it for personal projects sometimes. It's OK. I'm OK with JIRA in the right hands too though. You don't have to tweak every single knob and settings. You can practice some self restraint and avoid it nerd sniping you, probably.