Jira is a genuinely good tool that gets a bad reputation because most teams set it up wrong. Here's what actually works.
Jira gets a lot of hate from developers, but most of the time it's not Jira's fault — it's how the team configured it. I've seen the same tool feel invisible and helpful on one team, and feel like a second job on another. Here's what separates the two.
To Do, In Progress, In Review, Done. That's it for most teams. I've seen boards with nine custom statuses including things like "Pending Pending QA Sign-off" and nobody, including the person who made it, remembers when to use which one. Fewer statuses means fewer decisions, and fewer decisions means people actually keep the board updated.
Backlogs that never get groomed turn into a graveyard of tickets nobody will ever do. Fifteen minutes every couple weeks to close or merge stale tickets keeps the board something people can actually trust, instead of scrolling past 200 tickets to find the five that matter.
Put the ticket ID in the branch name (`ABC-123-fix-login`), not just in a comment somewhere. This is the single biggest thing that makes Jira useful for engineering — anyone can trace code back to the reason it was written, months later, without asking around.
This is the part almost every team gets wrong. Someone starts a ticket and forgets to move it. Someone finishes and the ticket sits there for days. The fix isn't a reminder bot, it's removing the manual step entirely — which is exactly what jitly start ABC-123 and jitly done do. Starting work moves the ticket to In Progress as a side effect, finishing moves it forward too, so the board always matches reality without anyone doing extra work.
If your standup update and your Jira board disagree, something's broken. Once status changes happen automatically instead of manually, the board becomes something you can trust in a meeting instead of something you have to double check.