[Too]

”Tickets should be minimal depending on the task. Creating a ticket that says 'update documentation' may take 10 seconds”

This type of placeholder-documentation is literally the WORST type of tracking you can have. And a sign that everybody in your company forgot the reason why this type of traceability was implemented in the first place.

If I review a PR that links to a Jira ticket that says absolutely nothing except “update documentation”. What’s the whole point?!

What’s worse is when people see a link to a Jira as an excuse to write bad commit messages.

I would much rather read a commit message detailing out the background and rationale of the change, rather than a nonsense commit message linking to another nonsense kpi-chasing Jira ticket.

PRs are code reviewed anyway so it’s not like you have a bonanza of unknown changes being pushed left and right. Code reviews not only catches coding bugs but also accountability within the team, eg “why are you refactoring something that works, when our backlog has 100 other more important things to do.”