Jira itself isn't the problem.. it's a decent bug tracker + with a whole lot of 'agile/scrum/sprint' tracking/planning features on top. That somehow attracts a

Jira itself isn't the problem.. it's a decent bug tracker + with a whole lot of 'agile/scrum/sprint' tracking/planning features on top. That somehow attracts a whole lot of 'process' focused middle managers who can absolutely kill any project... They want to 'use' jira - not focus on getting the product built. It doesn't help that most alternatives aren't enterprise-y enough I've seen enough efficient but somewhat chaotic projects move to jira, followed shortly by a bevy of managers who're brought in to manage jira, followed by the usual agile theatre & process overheads that's been a 'kiss of death You can argue that this isn't jira's fault.. but IMO, simpler tools require more work and act as a filter for the agile process minded types PS: I've also had extremely good experience on teams where Jira was used.. and it's always been because the 'agile process' guy was capable.. however, those have been few and far between