[cloudengineer]

Jira is a workflow tool, which also means that most of the issues mentioned here, can be sorted out between the PM and devs on who the workflow should be, and what the rituals for updates should/could be. Jira is flexible enough to accomodate it (mostly). From a developer perspective, some of the points maybe valid, but not from PM perspective.

It would also help if we could get an idea of what the alternatives are, that are better

Edit: Also looks like marketing for the product, than a valid article on Jira pitfalls.

[boudin]

I'm using Jira, not a huge fan (mostly because it's slow, the cloud version at least) and there's some clunkyness BUT every time I looked for alternatives it was either too opiniated (like SCRUM or nothing) or had really poor integration with dev tools. The big advantage of Jira is that you can customise it quite a bit and it has a good set of integrations and APIs.

I'm still thinking of moving away at some point but haven't found any alternative...

[pm90]

Try clubhouse