Jira
atlassian.com · Project and issue tracking
Atlassian's issue and project tracker for software and business teams.
186 open items · 151 source threads · 1 source type · updated 2026-09
This page rests on 151 Hacker News threads. No other public source type applies to Jira yet; every item links to the comment it came from.
No items match these filters.
Pain points 131
| Item | Area | Severity | Support | Last seen |
|---|---|---|---|---|
| Jira is consistently slow across many parts of the product The user finds Jira frustratingly slow throughout the product and says fixing a handful of major offenders would not materially improve the overall experience because many more remain. |
Performance | Blocks work | 5 sources | 2025-07 |
| ||||
| Jira feels overly complicated The user says Jira has felt complicated, and suggests its flexibility can lead to excessive complexity. They favor Jira over Azure DevOps but would prefer a simpler middle ground. |
UI & usability | Causes churn | 2 sources | 2024-09 |
| ||||
| Slow Jira pages disrupt issue discussions and daily work Jira Cloud takes seconds to switch views, so engineers minimize their use of the UI and move bug discussions to Slack, where they are harder to find. The slowness also makes reporting cumbersome. Affects: Engineers and project managers |
Performance | Causes churn | 2 sources | 2019-08 |
| ||||
| Jira with GreenHopper feels sluggish The user says sluggishness is their only complaint about using Jira with GreenHopper. |
Performance | Blocks work | 2 sources | 2026-05 |
| ||||
| Jira Cloud feels slow for quick tasks The user finds Jira Cloud painful when trying to work quickly, although they say it is usually only annoying and faster than it used to be. |
Performance | Blocks work | 2 sources | 2025-08 |
| ||||
| Jira and Confluence take too long to load Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 2 sources | 2023-03 |
| Jira pages load slowly Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 2 sources | 2020-08 |
| Jira feels less simple and slower than Linear Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 2 sources | 2020-07 |
| AI training data opt-out setting is missing Locked: summary and evidence are part of Sprint Pass and Pro |
Permissions & security | Causes churn | 1 source | 2026-04 |
| Jira Cloud lacks LDAP and directory-based account control Locked: summary and evidence are part of Sprint Pass and Pro |
Permissions & security | Causes churn | 1 source | 2016-06 |
| Jira disrupts sprint planning meetings Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2013-06 |
| Jira extension stops working with DNSSEC validation Locked: summary and evidence are part of Sprint Pass and Pro |
Reliability & bugs | Blocks work | 1 source | 2026-09 |
| Ticketing platforms are seen as employee surveillance Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Blocks work | 1 source | 2026-06 |
| GitHub tracking marks Jira tickets done too early Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2026-06 |
| Jira actions feel agonizingly slow Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2026-06 |
| Jira tags become useless when an instance is deleted Locked: summary and evidence are part of Sprint Pass and Pro |
Data export & migration | Blocks work | 1 source | 2026-06 |
| Jira UX and reporting features are inadequate Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2026-05 |
| Jira configuration can be controlled by disengaged administrators Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2026-05 |
| Engineers absorb Jira management when teams are understaffed Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Blocks work | 1 source | 2026-03 |
| Jira interface is slow and painful to navigate Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2026-03 |
| Work discussions and information get scattered across Jira and other tools Locked: summary and evidence are part of Sprint Pass and Pro |
Collaboration | Blocks work | 1 source | 2026-01 |
| Jira Cloud feels sluggish with overloaded templates Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2026-01 |
| Jira Cloud is slower and less configurable than self-hosted Jira Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2026-01 |
| Team member can only see their own Jira tasks Locked: summary and evidence are part of Sprint Pass and Pro |
Permissions & security | Blocks work | 1 source | 2026-01 |
| Jira search and bulk ticket operations are inadequate Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2025-12 |
| Jira reporting encourages ticket-count optimization over real progress Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2025-12 |
| Jira MCP requires daily reauthentication and hangs Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2025-11 |
| Jira AI features produce poor results Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Blocks work | 1 source | 2025-09 |
| Repeated status reporting across Jira and meetings Locked: summary and evidence are part of Sprint Pass and Pro |
Collaboration | Blocks work | 1 source | 2025-08 |
| Jira text edits can be lost when exiting accidentally Locked: summary and evidence are part of Sprint Pass and Pro |
Reliability & bugs | Blocks work | 1 source | 2025-08 |
| Jira slows down with excessive plugins Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2025-08 |
| Jira Cloud lacks rich markdown editing Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2025-08 |
| System-scope custom fields hurt Jira performance Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2025-07 |
| Jira configuration is easy to get wrong Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2025-07 |
| Jira has become bloated, slow, confusing, and buggy Locked: summary and evidence are part of Sprint Pass and Pro |
Reliability & bugs | Blocks work | 1 source | 2025-07 |
| Jira searches can omit matching issues Locked: summary and evidence are part of Sprint Pass and Pro |
Reliability & bugs | Blocks work | 1 source | 2025-07 |
| Jira workflows and team coordination were poorly configured Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2024-09 |
| Separate Atlassian instances prevented teams from seeing each other's work Locked: summary and evidence are part of Sprint Pass and Pro |
Collaboration | Blocks work | 1 source | 2024-09 |
| Sprint board is slow and loses custom filters Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2024-07 |
| Using Jira outside its intended use case exposes limitations and adds cost Locked: summary and evidence are part of Sprint Pass and Pro |
Pricing & plans | Blocks work | 1 source | 2024-02 |
| Jira migration lost historical case information Locked: summary and evidence are part of Sprint Pass and Pro |
Data export & migration | Blocks work | 1 source | 2024-02 |
| Product Discovery requires ideas before recording feedback Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2024-01 |
| Jira tickets are missing or too old to explain code changes Locked: summary and evidence are part of Sprint Pass and Pro |
Documentation | Blocks work | 1 source | 2024-01 |
| GitHub Projects lacks Jira’s advanced board and issue capabilities Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2023-10 |
| Jira’s customization options fuel project-planning paralysis Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2023-09 |
| Jira-Trello integration creates duplicate tickets with conflicting states Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2023-08 |
| Jira’s bureaucracy makes planning demotivating Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2023-08 |
| Jira's loading animations and small modals disrupt navigation Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2023-07 |
| Jira lacks support for three-point estimation Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2023-07 |
| HIPAA compliance requires a large Jira contract Locked: summary and evidence are part of Sprint Pass and Pro |
Permissions & security | Blocks work | 1 source | 2023-06 |
| Jira labels accumulate case variations in autocomplete Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2023-06 |
| Jira feels like an all-in-one tool that is hard to use Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2023-05 |
| Managed Jira can be slow Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2023-05 |
| Jira encourages task-focused product management Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Blocks work | 1 source | 2022-12 |
| Self-hosted Jira REST API returns no data across versions Locked: summary and evidence are part of Sprint Pass and Pro |
API & developer experience | Blocks work | 1 source | 2022-12 |
| Jira adds to growing subscription costs Locked: summary and evidence are part of Sprint Pass and Pro |
Pricing & plans | Blocks work | 1 source | 2022-11 |
| Self-hosted Jira outages disrupt access Locked: summary and evidence are part of Sprint Pass and Pro |
Reliability & bugs | Blocks work | 1 source | 2022-08 |
| SOC 2 controls restrict who can create and close Jira cards Locked: summary and evidence are part of Sprint Pass and Pro |
Permissions & security | Blocks work | 1 source | 2022-07 |
| Jira's integrated workflows add complexity and confusion Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2022-06 |
| Jira filters and workflow are confusing Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2022-04 |
| Customized on-prem Jira takes minutes to load boards and tickets Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2021-09 |
| Jira metrics used to reprimand employees Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2021-09 |
| Jira and Confluence feel slow and dated together Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2021-08 |
| Changing Jira dropdown options is buried in admin layers Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2021-06 |
| Team misses Phabricator's issue tracker after moving to Jira Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2021-05 |
| Jira is frustratingly slow to browse Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2021-02 |
| Jira Zapier integration omits the action-triggering user Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2021-02 |
| Jira ticket reporting felt like bureaucratic overhead Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2020-12 |
| Self-hosted Jira administration is difficult Locked: summary and evidence are part of Sprint Pass and Pro |
Self-hosting & upgrades | Blocks work | 1 source | 2020-10 |
| Cloud Jira is extremely slow Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2020-10 |
| Subtasks behave inconsistently with tasks Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2020-08 |
| Jira has frustrating UX and slow performance Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2020-07 |
| Keeping Jira ticket status in sync with completed PRs Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2020-05 |
| New Jira editor lacks the old formatting shortcuts Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2020-05 |
| Jira frontend feels slow while widgets load Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2020-04 |
| Jira’s UI complexity and sprint incentives hurt issue quality Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2020-03 |
| Splitting oversized Jira issues is frustrating Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2020-03 |
| Jira search misses exact phrase matches Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2019-05 |
| Jira redesign makes issue search and navigation harder Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2019-03 |
| Jira did not provide accountability or a reliable picture of work Locked: summary and evidence are part of Sprint Pass and Pro |
Collaboration | Blocks work | 1 source | 2019-01 |
| Unfixed bugs get lost among Jira issues Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2018-12 |
| Viewing Jira issues takes multiple seconds Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2018-11 |
| Jira takes too many clicks to reveal useful data Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2018-10 |
| Task estimates do not roll up to stories or epics Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2018-10 |
| Markdown syntax differs across Atlassian products Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2018-07 |
| Jira reports are inaccurate Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2018-07 |
| Jira and Stash backups are complicated Locked: summary and evidence are part of Sprint Pass and Pro |
Self-hosting & upgrades | Blocks work | 1 source | 2017-05 |
| Jira configuration takes too much time Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2017-01 |
| Jira workflows and configuration become difficult to manage Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2016-09 |
| Atlassian-hosted Jira offers limited performance control Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2016-09 |
| Jira bugs remain unresolved for long periods Locked: summary and evidence are part of Sprint Pass and Pro |
Reliability & bugs | Blocks work | 1 source | 2016-09 |
| Renaming dashboard components breaks underlying queries Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Blocks work | 1 source | 2015-10 |
| Submitting bug reports requires too much Jira navigation Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2015-07 |
| Jira is difficult to upgrade Locked: summary and evidence are part of Sprint Pass and Pro |
Self-hosting & upgrades | Blocks work | 1 source | 2015-07 |
| Jira version lacked Mercurial bookmark support Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2015-05 |
| Jira integration with HipChat is difficult to manage Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2014-10 |
| Jira is a high barrier for filing tickets Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2014-08 |
| Jira pages periodically take 10–30 seconds to load Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2014-06 |
| Jira project and issue administration has a steep learning curve Locked: summary and evidence are part of Sprint Pass and Pro |
Setup & onboarding | Blocks work | 1 source | 2014-05 |
| Jira UI and features feel clunky and poorly designed Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2013-06 |
| Unreliable Jenkins integration through Jira's SOAP API Locked: summary and evidence are part of Sprint Pass and Pro |
API & developer experience | Blocks work | 1 source | 2013-01 |
| Jira is slow and clunky for issue reporters Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2012-10 |
| Jira is slow and tedious to use Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2012-05 |
| Jira price rose sharply with the 4.0 license change Locked: summary and evidence are part of Sprint Pass and Pro |
Pricing & plans | Blocks work | 1 source | 2009-11 |
| Jira feels slow and reloads the whole page on each click Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Blocks work | 1 source | 2008-10 |
| Jira pricing is seen as too high Locked: summary and evidence are part of Sprint Pass and Pro |
Pricing & plans | Blocks work | 1 source | 2007-10 |
| Jira requires a separate SSO login Locked: summary and evidence are part of Sprint Pass and Pro |
Setup & onboarding | Annoyance | 1 source | 2026-06 |
| Jira's many options make navigation confusing Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2026-06 |
| Jira creates a translation burden for developers Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2026-05 |
| Tracing a bug requires searching across multiple systems Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Annoyance | 1 source | 2026-03 |
| Finding Jira tickets is slow during debugging Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2025-03 |
| Jira subtasks are frustrating to use Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2025-01 |
| Jira ticket-created toast disappears too quickly Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2024-08 |
| Tickets are valued over completed work Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2024-06 |
| Jira is part of a fragmented workflow for ERP data entry Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Annoyance | 1 source | 2023-12 |
| Slow Jira aggregation in the web app Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Annoyance | 1 source | 2023-06 |
| Jira notifications add to the overload of team alerts Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2023-03 |
| Jira's web UI is annoying Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2022-10 |
| Jira does not linkify selected text when pasting a URL Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2022-06 |
| Building Jira forms and workflows is cumbersome Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Annoyance | 1 source | 2022-06 |
| Interface changes hide familiar features Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2021-01 |
| Monospaced text syntax differs between ticket creation and editing Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2020-12 |
| Jira rejects field changes after users enter them Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2020-07 |
| Jira becomes too complex in practice Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2020-07 |
| Jira’s Mac-style interactions behave inconsistently Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2020-06 |
| Jira becomes an outdated afterthought Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2020-04 |
| Jira estimates and velocity provide little insight Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Annoyance | 1 source | 2018-10 |
| Jira's UI is more annoying than Slack's Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2017-07 |
| Administering Jira is annoying Locked: summary and evidence are part of Sprint Pass and Pro |
Setup & onboarding | Annoyance | 1 source | 2017-01 |
| Jira project management feels cumbersome and slow Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Annoyance | 1 source | 2015-07 |
| Jira is expensive and cluttered Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2007-10 |
Feature requests 16
| Item | Area | Severity | Support | Last seen |
|---|---|---|---|---|
| Allow users to hide Jira AI buttons individually Jira's AI suggestions and writing buttons are unwanted, but users cannot turn them off for themselves; only an admin can disable them globally. The post notes an issue requesting individual-user controls has many votes. Affects: Jira users |
UI & usability | Blocks work | 1 source | 2026-08 |
| ||||
| Standardize task tracker data for easier tool switching The commenter wants an interoperability standard for task-management tools, saying repeated reinvention of common task concepts makes moving between trackers tedious. Affects: People moving between task trackers |
Data export & migration | Blocks work | 1 source | 2025-06 |
| ||||
| Automate Jira task creation and status updates The post proposes using AI to create tasks, update their states, and mark them complete from information in chat and GitHub, rather than requiring users to keep tasks current manually. |
Customization | Blocks work | 1 source | 2024-09 |
| ||||
| Add configurable timed notification digests The commenter says Jira notifications are overwhelming and asks for a configurable timed digest, noting that the issue has remained unresolved for years and discourages adoption. Affects: Jira and Confluence users |
UI & usability | Blocks work | 1 source | 2023-10 |
| ||||
| Add structured QA test plans QA teams need structured test plans to organize testing activities, release-related tasks, and work that is difficult to automate. Free-form Jira stories do not provide enough structure for this work. Affects: QA teams |
Customization | Blocks work | 1 source | 2023-10 |
| ||||
| Structure product requirements beyond free-form issues Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2023-10 |
| Use consistent markup across Jira Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2021-01 |
| Share completed work directly on Jira tickets Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2019-01 |
| Create pull requests directly from Jira tasks via GPT Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Annoyance | 1 source | 2026-02 |
| Add settings to restore the previous sorting and comment-box behavior Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2023-10 |
| Allow multiple assignees on a Jira task Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Annoyance | 1 source | 2021-08 |
| Make moving tickets between projects easier Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2020-08 |
| Add Markdown Here support for Jira Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Annoyance | 1 source | 2017-11 |
| Faster Jira alternative with a focused feature set Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2015-07 |
| More powerful queries and dashboard customization Locked: summary and evidence are part of Sprint Pass and Pro |
Reporting & analytics | Annoyance | 1 source | 2014-04 |
| Allow bug reports without creating an account Locked: summary and evidence are part of Sprint Pass and Pro |
Setup & onboarding | Annoyance | 1 source | 2007-10 |
Workarounds 13
| Item | Area | Severity | Support | Last seen |
|---|---|---|---|---|
| Uses a filesystem interface to browse Jira issues The user built a Jira-as-filesystem project to make interacting with Jira less frustrating, organizing issues and fields as directories and files. |
UI & usability | Blocks work | 1 source | 2024-10 |
| ||||
| Bug reports omit details to avoid exposing health information Because Jira lacks the needed HIPAA coverage, reports avoid including details resembling the actual bug, forcing clinicians and customer service to take extra steps to file issues. Affects: Clinicians and customer service |
Permissions & security | Blocks work | 1 source | 2023-06 |
| ||||
| Automations imitate cross-project version management Jira Versions cannot be shared across projects, so the team automated version management to imitate that capability. |
Customization | Blocks work | 1 source | 2023-06 |
| ||||
| Data residency constraints force use of Jira Data Center Some customers are legally required to keep data on-premises, but Atlassian cannot promise their data will remain in-country. Using Jira Data Center is described as the available option, while smaller customers face a substantial problem. Affects: Customers legally required to use an on-premise solution |
Self-hosting & upgrades | Blocks work | 1 source | 2022-04 |
| ||||
| Ignored Jira suggestions leave improvement ideas without a path The company directs employees to file ideas in a Jira suggestions project, but tickets dating back to 2014 have been ignored. The poster sees this as a way to dismiss suggestions and is looking elsewhere for work. Affects: Employees at a conservative company |
Collaboration | Blocks work | 1 source | 2021-10 |
| ||||
| Use a Slack chatbot to create Jira issues Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2019-08 |
| Teams move Jira project planning into Excel Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Blocks work | 1 source | 2019-05 |
| Use Aha for missing Jira roadmap functionality Locked: summary and evidence are part of Sprint Pass and Pro |
Integrations | Blocks work | 1 source | 2018-10 |
| AI handles routine Jira ticket creation Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2026-08 |
| Use Claude skills to avoid Jira's interface Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2026-03 |
| Use a bookmarklet to navigate to Jira tickets Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Annoyance | 1 source | 2023-10 |
| Tracking Jira bugs in an Excel spreadsheet Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Annoyance | 1 source | 2020-12 |
| Emacs script automates Jira-based branch naming Locked: summary and evidence are part of Sprint Pass and Pro |
API & developer experience | Annoyance | 1 source | 2020-01 |
Switching reasons 26
| Item | Area | Severity | Support | Last seen |
|---|---|---|---|---|
| Extreme slowness may lead the team to leave Jira The user says Jira is so slow that they have tried to persuade a manager to switch to GitLab Issues, and expects the team may drop Jira. Affects: The user's team |
Performance | Causes churn | 2 sources | 2024-02 |
| ||||
| Company moving off Jira The author welcomes a notification that their company was moving away from Jira, indicating dissatisfaction with the product, though they do not specify a Jira feature or problem. |
Other | Causes churn | 1 source | 2026-03 |
| ||||
| Team left Jira because GitHub integration caused hassle The team switched from Jira to GitHub Issues because the Jira–GitHub integration was poor and keeping the systems in sync created hassle. They also cited cost savings. Affects: Software team |
Integrations | Causes churn | 1 source | 2026-03 |
| ||||
| Moving fine-grained task management from Jira to markdown The author says their team will stop using Jira for fine-grained task management and move that work to markdown files, with higher-level tasks potentially tracked in Linear. Affects: Developers |
Other | Causes churn | 1 source | 2026-03 |
| ||||
| Jira's annual price was unacceptable The team says Jira's annual cost of $26,000 per customer was unacceptable and reports using Plane instead. Affects: Regulated-industry team |
Pricing & plans | Causes churn | 1 source | 2025-07 |
| ||||
| Jira license costs prompted a move to Azure DevOps Locked: summary and evidence are part of Sprint Pass and Pro |
Pricing & plans | Causes churn | 1 source | 2024-09 |
| Team member wants to leave Jira but cannot drive changes Locked: summary and evidence are part of Sprint Pass and Pro |
Customization | Causes churn | 1 source | 2024-05 |
| Developer left Jira for a less burdensome project tracker Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2023-10 |
| User wants to move from Jira to GitLab issues Locked: summary and evidence are part of Sprint Pass and Pro |
Pricing & plans | Causes churn | 1 source | 2023-07 |
| Team members were blocked in Jira workflows Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2023-02 |
| Team switched from Jira after low issue participation Locked: summary and evidence are part of Sprint Pass and Pro |
Collaboration | Causes churn | 1 source | 2022-06 |
| Jira UX and performance prompted a move to Shortcut Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Causes churn | 1 source | 2022-04 |
| Users want alternatives to frustrating Jira task management Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2022-04 |
| Team replaced Jira with GitHub Issues and Projects Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2022-04 |
| Jira Cloud’s poor performance drove a move to Clubhouse Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Causes churn | 1 source | 2020-06 |
| Jira feels too heavy for simple issue tracking Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Causes churn | 1 source | 2017-08 |
| Jira experience makes user wish for another site Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2016-09 |
| Teams moved from Jira back to Excel Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Causes churn | 1 source | 2016-03 |
| Switched from Basecamp to Jira Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Causes churn | 1 source | 2014-02 |
| Would prefer Pivotal Tracker over Jira for agile planning Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Causes churn | 1 source | 2013-06 |
| Moved from Jira to Pivotal for a simpler workflow Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Causes churn | 1 source | 2013-02 |
| Jira felt slow and complicated Locked: summary and evidence are part of Sprint Pass and Pro |
Performance | Causes churn | 1 source | 2011-11 |
| Uses Obsidian Tasks instead of Jira Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2025-09 |
| Jira ticketing disrupts sustained work on large tasks Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Blocks work | 1 source | 2020-03 |
| Jira’s crowded UI drove interns to GitHub Issues Locked: summary and evidence are part of Sprint Pass and Pro |
UI & usability | Blocks work | 1 source | 2018-08 |
| Team moved from internal Jira to a public backlog Locked: summary and evidence are part of Sprint Pass and Pro |
Other | Blocks work | 1 source | 2016-06 |