Jira Problems & Issues

Users describe Jira as 'bloated and ridden with technical debt.' Creating a ticket can take 10 seconds to open. The software runs 'embarrassingly slow' with 10-20 second hangs when navigating. Users report 'you can make yourself a cup of tea while waiting for all the issues to load.' Page refresh downloads batch.js files that can be 26MB causing huge lag.

Atlassian documentation acknowledges that 'performance may slowly deteriorate due to stuck threads and thread pool exhaustion caused by third-party apps.' The plugin ecosystem that makes Jira powerful also makes it unstable. Batch.js files from plugins can reach 26MB, causing massive lag.

Jira has a 'steep learning curve with a ton of features, with many that will never be used by an average business.' Non-tech-savvy users find navigation complex and confusing. The 'convoluted setup process' with different modules for different team types frustrates new users. Many organizations fall into 'Jira Hell' by over-customizing.

After recent UI updates, users report Jira has become 'painfully slow' with every click or keyboard input taking 4-5 seconds. Community forums have threads titled 'Anyone else hate the new Jira experience?' Many feel 'it was good the previous version, but the new one is anti-intuitive, slow and unreliable.'

Teams that use Jira, when asked what they think, typically respond with 'it's fine, I guess' rather than enthusiasm. For simple project tracking, Jira is 'over-engineering' and its complexity becomes a burden. Non-development teams often find it unsuitable for their needs.

Jira Query Language (JQL) is powerful but has a significant learning curve. Finding specific issues without knowing JQL can be difficult. Teams must invest time learning the query syntax to effectively search and filter their work, adding to overall adoption friction.

On Jira's free plan, you are capped at exactly 10 users. If you hire your 11th employee or add a freelancer, you are forced to start paying for ALL users immediately. Unlike competitors like Linear (unlimited free users), this creates sudden billing spikes for growing startups.

Many essential features require paid third-party apps from the Atlassian Marketplace. Time tracking, advanced reporting, and integrations often need additional licenses. Total cost of ownership increases significantly beyond base subscription when accounting for plugins, training, and admin time.

Jira automation is metered: Free gets 150 automation steps per month for the whole site, Standard 400 steps per user, Premium 750 and Enterprise 1,000. Since Atlassian ended unlimited single-project rules in late 2023, admins report rules being throttled and having to upgrade to Premium to keep workflows running; users have asked for incremental top-ups on Standard instead.

Atlassian's official pricing page now lists Jira Standard at $8.48 per user per month (previously $8.15) and Premium at $15.56. Every licensed user is billed whether or not they log in, so the increase compounds for large sites and is on top of any marketplace app costs.

Rovo AI is bundled in paid plans but limited by pooled monthly credits (25 per user on Standard, 70 on Premium, 150 on Enterprise); Free has no Rovo. Community complaints focus on confusing credit-based pricing, agent questions consuming several credits each, and planned overage charges.

Capterra reviews highlight 'recurring bugs and reliability concerns' and 'frequent slowdowns with scale.' Users report glitches, confusing error messages, and unreliable integrations often requiring troubleshooting or workarounds. Some days the site is 'quite laggy when navigating around.'

A recurring support topic: users stop getting Jira emails because of personal notification settings, notification schemes that don't include them, workflow transitions firing a Generic Event, missing Browse permission, or suppressed addresses that only Atlassian Support can unsuppress.

Unlike competitors that provide 24/7 support on all plans, Jira restricts faster support to highest tiers. Organizations with limited technical expertise struggle with self-service support. Complex configuration issues can go unresolved without premium support access.