Do development teams often game JIRA metrics in practice?

[elizabeths]

At my old company, managers focused heavily on JIRA numbers for performance reviews. This made our dev teams start gaming the system pretty badly.

Here’s what I saw happening:

• Teams would reclassify obvious bugs as “enhancements” to make bug counts look better
• After tickets were already closed, people would go back and mark them as “critical” or “blocker” to boost their high-priority fix numbers
• Single problems got split into multiple tickets, then most got closed without any actual code changes
• Customer issues got marked as resolved before anyone checked if the fix worked, then new non-customer tickets were created if problems persisted

Looking at the dashboard made everything seem amazing, but it was completely fake. Management loved bragging about closing thousands of tickets per release, but nobody questioned why we had thousands of issues to begin with.

When I brought this up, my manager said this was standard practice and I just didn’t understand enterprise development workflows yet.

Is this actually normal behavior? Do other companies manipulate their tracking tools like this?

[Luna23]

totally agree! it’s wild how those dashboards look great but don’t reflect the real struggles. I’ve seen teams do similar stuff—just to get those performance scores. it’s not about the numbers! management should focus on actual work done, not just shiny stats.

[Tom_89Paint]

This happens way more than companies want to admit. I worked somewhere that rolled out JIRA velocity tracking - within months it was completely useless. Devs started splitting simple tasks into tons of subtasks just to pump up story points. Product owners gamed the priority system to make their features seem urgent. The worst part? Upper management compared team velocities across totally different projects without any context. Teams inflated estimates so they wouldn’t look slow next to others. Sprint planning became math homework instead of actual planning. The crazy part is all this gaming actually hurt development because people spent more time managing tickets than writing code.