141 engineers on Hacker News describe using Jira first-hand: 23 endorse it, 52 regret it, 14 are mixed.
“even on Jira we lose cases as teams end and hand off the code, and the Jira project is closed so no one else can access it.”
regret · production · Izkata · 2026-06-05 · source ↗ · wrong label?“The integration of the two wasn't great so we switched to GitHub issues and kicked Jira to the curb.”
regret · production · cheema33 · 2026-03-12 · source ↗ · wrong label?“after we migrated to the cloud version, this option disappeared and the ticket is flooded with commit messages making it essentially useless”
regret · production · dvfjsdhgfv · 2026-03-12 · source ↗ · wrong label?“Jira had to get REALLY bad before we switched to Linear for example”
regret · production · theshrike79 · 2025-10-08 · source ↗ · wrong label?“we switched to a SaaS version of Jira recently and things became about an order of magnitude slower.”
regret · production · asoneth · 2025-08-08 · source ↗ · wrong label?“We run an airgapped version of JIRA... Performance is in the gutter.”
regret · production · crabbone · 2025-07-23 · source ↗ · wrong label?“we run it for a team of < 10 developers on a small VM and it just works.”
endorse · production · bpt3 · 2025-07-22 · source ↗ · wrong label?“Jira and Bitbucket were hands down the slowest of the bunch to boot”
regret · production · p2detar · 2025-02-04 · source ↗ · wrong label?“We ditched Jira to go all-in on GH... the Jira experience seems hostile to it.”
regret · production · yakshaving_jgt · 2025-01-19 · source ↗ · wrong label?“I tried Jira for the first time and right from the start they spammed me with upsells.”
regret · personal · jarsin · 2024-12-24 · source ↗ · wrong label?“They've been pushing customers to their cloud versions pretty hard and holding back features. Jira and Confluence are decent”
mixed · production · acdha · 2024-12-06 · source ↗ · wrong label?“We used jira for live incident handling back in 2015 at a young company. It was horrendous.”
regret · production · raffraffraff · 2024-01-08 · source ↗ · wrong label?“JIRA is a nightmare (source: Former JIRA admin).”
regret · production · ChrisMarshallNY · 2023-10-23 · source ↗ · wrong label?“Jira is awful at Kanban. Trello was great... Jira is an inescapable black hole”
regret · production · WorldMaker · 2023-08-16 · source ↗ · wrong label?“We were using their hosted service, and it was a dumpster fire inside a meth lab...”
regret · production · veidr · 2023-05-16 · source ↗ · wrong label?“ugly but feature complete is better than easy to work with and missing key features”
endorse · production · yjftsjthsd-h · 2023-05-04 · source ↗ · wrong label?“Our experience with BitBucket in the Netherlands has been that it's slow, almost as bad as Jira.”
regret · production · difosfor · 2023-04-18 · source ↗ · wrong label?“We've switched from JIRA to Linear.app more than year ago, and never looked back. With JIRA our team members were getting blocked in the flows quite a bit”
regret · production · bndr · 2023-02-10 · source ↗ · wrong label?“We use cloud Jira, without any sort of crazy customization. ... Their p50 time is already unacceptable, and their p90 time is completely absurd.”
regret · production · flaviut · 2022-12-09 · source ↗ · wrong label?“we migrated from JIRA to Linear for our small team, and haven't looked back.”
regret · production · nemothekid · 2022-10-14 · source ↗ · wrong label?“Overall, we are very happy with Jira and it's worth the cost... Jira is kinda slow sometimes... And then Atlassian comes along and rug-pulls on-prem Jira.”
mixed · production · throwaway3l2ff · 2022-06-20 · source ↗ · wrong label?“It's just more powerful, and has ways of keeping tickets from falling into a black hole.”
mixed · production · labster · 2022-06-20 · source ↗ · wrong label?“we weren't managing either very well in Jira. It's easy to say we will lose a lot of history”
regret · production · TheNewsIsHere · 2022-05-02 · source ↗ · wrong label?“Now we've moved to Jira + Zephyr for test management + Enzyme. I can't say I recommend it.”
regret · production · jrowley · 2022-04-19 · source ↗ · wrong label?“It's much better than JIRA ever was, both from a UX perspective and an implementation/performance perspective.”
regret · production · nicoburns · 2022-04-13 · source ↗ · wrong label?“Writing this while I desperately wait for Jira to render the page.”
regret · production · ilayn · 2021-12-06 · source ↗ · wrong label?“Takes like 4 screens to reparent a task. What a load of garbage. Makes me wanna quit after years of work, just because we switched to Jira.”
regret · production · dzhiurgis · 2021-10-15 · source ↗ · wrong label?“We are on JIRA now, and it's … JIRA.”
regret · production · cygned · 2021-08-29 · source ↗ · wrong label?“Asana has been an incredible upgrade from JIRA. We switched two weeks ago”
regret · production · xvector · 2021-06-25 · source ↗ · wrong label?“I used to complain about Jira for similar reasons... I want my simple and fast Jira back!”
endorse · production · Viliam1234 · 2021-05-16 · source ↗ · wrong label?“JIRA is waaaayyy tooooo slow. Nobody wanted to use it day-to-day.”
regret · production · veidr · 2020-12-31 · source ↗ · wrong label?“I've been using Jira for many years in different organisations. Just pointing out that Java has nothing to do with how bad Jira has become.”
regret · production · bitcharmer · 2020-12-31 · source ↗ · wrong label?“We use JIRA specifically for this... Not saying JIRA is perfect by any means, but this works quite well for us.”
endorse · production · magicalhippo · 2020-12-31 · source ↗ · wrong label?“it is abysmally slow. At least their Cloud offering is, which is the core product we use at my job.”
mixed · production · tlapinsk · 2020-12-31 · source ↗ · wrong label?“We eventually transitioned to Jira and it was good.”
endorse · production · losthobbies · 2020-12-31 · source ↗ · wrong label?“now we're fortunately off next-gen Jira”
regret · production · as-j · 2020-12-23 · source ↗ · wrong label?“I've been using JIRA for years now, and it never gets any easier or better. I can never find what I want, I can never remember how to do things.”
regret · production · blakesterz · 2020-12-09 · source ↗ · wrong label?“We noticed the cloud offering became consistently worse over time for the past two or three years.”
regret · production · stingraycharles · 2020-11-07 · source ↗ · wrong label?“I am a fan of the newer Portfolio/Plan functionality in JIRA”
endorse · production · nyi · 2020-11-07 · source ↗ · wrong label?“Jira is over-complicated and a server administration nightmare.”
regret · production · dangus · 2020-10-20 · source ↗ · wrong label?“JIRA is as system that is hilariously hobbled by two forces - JIRA admins and management”
regret · production · p_l · 2020-10-19 · source ↗ · wrong label?“served all the needs and it was amazing to move tickets between departments while maintaining history”
mixed · production · 10 yr · pfranz · 2020-10-17 · source ↗ · wrong label?“Jira is particularly bad, because it is slow and complicated, but switching to simpler tools doesn't make that underlying problem go away.”
regret · production · jrockway · 2020-07-11 · source ↗ · wrong label?“I disliked JIRA and we switched to Microsoft DevOps about a year ago. Now I really miss JIRA.”
mixed · production · replyguy912 · 2020-05-16 · source ↗ · wrong label?“I used to use GitHub tickets and JIRA, but over time I needed organization that didn't cause a lot of busy work.”
regret · production · matt_lo · 2019-12-30 · source ↗ · wrong label?“we 'switched to be more agile.' (This just meant using JIRA and tracking sprint efficiency wrong).”
regret · production · uxp100 · 2019-12-11 · source ↗ · wrong label?“we use Jira at work and I can't stand it.”
regret · production · iLemming · 2019-12-10 · source ↗ · wrong label?“It's done absolutely nothing but cause problems, cause friction, frustration.”
regret · production · philliphaydon · 2019-03-05 · source ↗ · wrong label?“we use Jira at work and it has been serving us well. Really, I can't complain.”
endorse · production · znpy · 2018-12-10 · source ↗ · wrong label?“We use Jira but it has such a vast disconnect from how the mind works.”
regret · production · rhacker · 2018-12-10 · source ↗ · wrong label?“JIRA is a pretty flexible tool. We use it primarily because it is a ticket list that we've been able to get approved in our corporate IT system.”
endorse · production · moron4hire · 2018-12-10 · source ↗ · wrong label?“Jira used to be hip and all... these days it is a monster and reminds of me HP QC monstrosity”
regret · production · democracy · 2018-12-09 · source ↗ · wrong label?“JIRA is very far from perfect but like it many times more.”
mixed · production · 1 yr · aik · 2018-11-30 · source ↗ · wrong label?“After a bunch of trial and error, I've landed on a workflow I like with JIRA, but it painfully slow”
mixed · production · bradstewart · 2018-10-18 · source ↗ · wrong label?“it works for coordinating ~200 folks in a starting-to-get-there "Agile" model”
mixed · production · _jal · 2018-08-05 · source ↗ · wrong label?“JIRA has those pretty reports that someone wanted and that are never accurate.”
regret · production · actionowl · 2018-07-26 · source ↗ · wrong label?“We switched from Jira, so maybe I'm finally just getting over my Stockholm syndrome”
regret · production · shijie · 2018-07-09 · source ↗ · wrong label?“Just YouTrack it :) - much more responsive from JIRA (I do not work neither for Atlassian, nor JetBrains, but we use both products @ work.”
regret · production · malkia · 2017-12-25 · source ↗ · wrong label?“With a cross-discipline team focused on delivering a few things (basically epics/features/whatever) at once, I love JIRA.”
endorse · production · everythingswan · 2017-09-04 · source ↗ · wrong label?“We moved to JIRA. Lost the simplicity but its a lot snappier”
mixed · production · infecto · 2017-08-29 · source ↗ · wrong label?“I have yet to use another ticket system for software development that is as decent to use as JIRA... I CHOSE JIRA for my company.”
endorse · production · manyxcxi · 2017-01-10 · source ↗ · wrong label?“the result was much better than any of the individual ticketing systems with the huge benefit of just opening a ticket anywhere”
endorse · production · pfranz · 2017-01-09 · source ↗ · wrong label?“We're a small company (< 20) and we like Jira. There's nothing that offers near the same functionality. It's worth every penny.”
endorse · production · Confusion · 2017-01-09 · source ↗ · wrong label?“I've been using JIRA for a long time - probably on and off since about 2010 - and I actually think it's a lot better now than it ever was.”
endorse · production · 6 yr · bshimmin · 2016-12-09 · source ↗ · wrong label?“we screwed JIRA also and it's way easier to maintain”
regret · production · merb · 2016-11-23 · source ↗ · wrong label?“So Atlassian pushed us on to Jira... what an epic failure that was.”
regret · production · agentgt · 2016-09-09 · source ↗ · wrong label?“we landed on JIRA, no matter how much we wanted to find something better.”
mixed · production · themartorana · 2016-06-28 · source ↗ · wrong label?“we wrote integration into our GUI apps for users to create tickets... The best part was being able have end users open up a ticket wherever they were most comfortable”
endorse · production · pfranz · 2016-06-27 · source ↗ · wrong label?“JIRA has been painful to use as a developer in the trenches for the 7 years and 3 companies I've used it at”
regret · production · 7 yr · girvo · 2015-12-10 · source ↗ · wrong label?“Then we switched to JIRA, and it was only slightly less terrible.”
regret · production · amyjess · 2015-10-02 · source ↗ · wrong label?“I am a big fan of jira. It's definitely more complicated than a simple bug tracker”
endorse · production · fletchowns · 2015-10-01 · source ↗ · wrong label?“I sometimes hate the complexity of Jira, but at the moment it's better suited for certain projects then our own.”
mixed · production · janlukacs · 2015-08-03 · source ↗ · wrong label?“We just updated Jira at my job, it feels pretty snappy.”
endorse · production · 0.17 yr · fokinsean · 2015-07-30 · source ↗ · wrong label?“The automation between JIRA and Stash is also 10% awesome, with that other 10% lost because you can't specify a code reviewer in a Stash pull request”
regret · production · tomphoolery · 2015-07-30 · source ↗ · wrong label?“We use bug tracking software. JIRA. It's horrible. Click here, click there, this screen closes, that one opens”
regret · production · RogerL · 2015-07-20 · source ↗ · wrong label?“the Jira version we switched to didn't support bookmarks.”
regret · production · Skinney · 2015-05-01 · source ↗ · wrong label?“We migrated from trac to jira a couple years ago and it actually wasn't that bad. ... Jira really shines on larger projects though.”
endorse · production · 2 yr · fletchowns · 2014-12-16 · source ↗ · wrong label?“I'm a part time JIRA, Fisheye, Crucible admin (on site ~ 250 users) and my word both those things make me cry at least once a week with problems.”
regret · production · bananas · 2014-04-22 · source ↗ · wrong label?“We switched to Jira and couldn't be happier.”
endorse · production · pooshoot · 2014-02-05 · source ↗ · wrong label?“I decided to centralize it all with Atlassian's OnDemand suite. Cheap and chips for small teams! We use Jira w/ Agile”
endorse · production · semerda · 2013-12-14 · source ↗ · wrong label?“We switched to Jira about six months ago and it has been very painful. The worst parts of my week are when I have to interact with Jira.”
regret · production · 0.5 yr · bobbyi_settv · 2013-06-05 · source ↗ · wrong label?“I'm really glad we've switched to Jira[1] after fighting with pivotal for a couple of months.”
endorse · production · st0p · 2013-02-17 · source ↗ · wrong label?“GitHub issue tracking and wiki suck compared to Jira/Confluence. So we run GH Enterprise + JIRA + Confluence.”
endorse · production · meh01 · 2013-01-22 · source ↗ · wrong label?“we use Jira with GreenHopper and it's great. sluggishness is my only complaint.”
mixed · production · SonicSoul · 2012-12-17 · source ↗ · wrong label?“We also integrate Jenkins with JIRA, so as soon as Jenkins builds something, pass/fail... a comment is automatically added there”
endorse · production · X-Istence · 2012-03-14 · source ↗ · wrong label?“Jira was used at the first tech company I worked at. Waaaaay too process focused. Detracted from those who actually do work.”
regret · production · malandrew · 2011-12-14 · source ↗ · wrong label?“Every tool ends up feeling too restrictive, too big brother, and too TPS-report-coversheet.”
mixed · production · akeefer · 2011-12-01 · source ↗ · wrong label?“We switched to Jira after getting annoyed at Mantis once too often. Haven't regretted it one single bit.”
endorse · production · Confusion · 2011-02-22 · source ↗ · wrong label?“JIRA tickets get created, and we ask AI to reference that ticket, code to it, and create a PR.”
neutral · production · thraway3837 · 2026-07-08 · source ↗ · wrong label?“This is the way we did it when we used JIRA.”
neutral · production · dualvariable · 2026-06-05 · source ↗ · wrong label?“we evaluated them in 2023, because we wanted to move off JIRA”
neutral · production · pas · 2026-03-27 · source ↗ · wrong label?“we migrated from jira -> linear, pagerduty -> oncallmanager”
neutral · production · finedev · 2026-01-24 · source ↗ · wrong label?“we've migrated from Bugzilla to Fogbugz to Jira”
neutral · production · Izkata · 2025-12-27 · source ↗ · wrong label?“a service that reviews pull requests and updates documentation/JIRA accordingly when they are merged”
neutral · production · epolanski · 2025-12-15 · source ↗ · wrong label?“I usually have several browser tabs open for Jira, and they all have the same company logo as the favicon”
neutral · production · NotMichaelBay · 2025-12-11 · source ↗ · wrong label?“Even things like Jira we use them only for the bare minimum and we refer to sheets to see how things are going.”
neutral · production · JaumeGreen · 2025-12-05 · source ↗ · wrong label?“publish a list of PRs and links to the tickets in Jira.”
neutral · production · mschild · 2025-10-19 · source ↗ · wrong label?“Issue tracking is a 17 year old JIRA project with a default workflow.”
neutral · production · 17 yr · crinkly · 2025-07-23 · source ↗ · wrong label?“For projects we moved to Jira some time ago, so little to do here.”
neutral · production · Propelloni · 2024-09-22 · source ↗ · wrong label?“We use JIRA at work. We have very, very simple processes. We create issues, we assign them, we resolve them”
neutral · production · magicalhippo · 2024-06-30 · source ↗ · wrong label?“rename the chat to the Jira Ticket #”
neutral · production · WesleyJohnson · 2024-03-01 · source ↗ · wrong label?“we switched from Bugzilla to FogBugz to Jira in my time.”
neutral · production · Izkata · 2024-02-02 · source ↗ · wrong label?“engineers use a separate ticket system like Jira to instruct the finance people how to do the data entry in SAP.”
neutral · production · qetuo13579 · 2023-12-25 · source ↗ · wrong label?“I wrote quite a few small tools to "integrate" with other stuff we use (Jira, BitBucket, Toggl).”
neutral · production · mbork_pl · 2023-12-02 · source ↗ · wrong label?“Having used linear (we switched to Jira)”
neutral · production · xp84 · 2023-06-01 · source ↗ · wrong label?“we modified and patched it to become a realtime project management system and we ditched odoo, jira”
neutral · production · v3ss0n · 2023-02-14 · source ↗ · wrong label?“documents on the jira ticket how they verified stuff”
neutral · production · sethammons · 2022-12-16 · source ↗ · wrong label?“a JIRA ticket consists of some attachment with "this please" is handed to me”
neutral · production · KronisLV · 2022-12-16 · source ↗ · wrong label?“Once experienced people joined the team we switched to jira.”
neutral · production · adulion · 2022-12-06 · source ↗ · wrong label?“needs to takes Jira issues as input and produce Gitlab merge requests as output”
neutral · production · ChuckNorris89 · 2022-11-21 · source ↗ · wrong label?“I use GitHub, Jira, and Outlook integrations for slack”
neutral · production · charrondev · 2022-08-20 · source ↗ · wrong label?“We switched from Jira and our team's participation on issues went through the roof.”
neutral · production · new_here · 2022-06-30 · source ↗ · wrong label?“When we migrated away from JIRA, we scripted it such that the JIRA issue numbers were recorded in the newly migrated issues”
neutral · production · rwiggins · 2022-04-13 · source ↗ · wrong label?“We switched off to Jira + Confluence for feature parity that Clubhouse lacked”
neutral · production · tedmiston · 2022-02-15 · source ↗ · wrong label?“ticket: is a branch for each JIRA ticket not each feature.”
neutral · production · PontiacParade · 2021-12-17 · source ↗ · wrong label?“ticket: is a branch for each JIRA ticket not each feature.”
neutral · production · lmm · 2021-12-17 · source ↗ · wrong label?“We used to pay for GH Enterprise and run Jira/Confluence/Bamboo/etc/etc.”
neutral · production · foobarbazetc · 2021-06-23 · source ↗ · wrong label?“I think there should be some content about how our HR teams use Jira coming out soon”
neutral · production · ccwilson10 · 2020-12-31 · source ↗ · wrong label?“Do we need a new Azure queue? That's a Platform ticket in JIRA.”
neutral · production · twh270 · 2020-12-21 · source ↗ · wrong label?“One team actually kept an old redmine VM instance running mostly based on my personal use long after we'd migrated to JIRA”
neutral · production · wcarss · 2020-10-05 · source ↗ · wrong label?“which would use the Jira API to fetch any comments made in the last 10 seconds”
neutral · production · mac-chaffee · 2020-06-28 · source ↗ · wrong label?“having dabbled with JIRA a few times.”
neutral · personal · tomrandle · 2019-09-11 · source ↗ · wrong label?“We switched from JIRA to youTrack”
neutral · production · kull · 2019-08-31 · source ↗ · wrong label?“A few years ago we migrated from Jira to Gitlab.”
neutral · production · Spidler · 2019-08-27 · source ↗ · wrong label?“yes, we do use Agile/Jira, doing 2-week or more Sprints”
neutral · production · manish_gill · 2018-12-26 · source ↗ · wrong label?“We try to capture too much design in the various types of tickets, but that in my opinion is wrong”
neutral · production · temporallobe · 2018-12-10 · source ↗ · wrong label?“We had this issue several times when we migrated from Trello to Jira.”
neutral · production · tbarbugli · 2018-10-05 · source ↗ · wrong label?“We replaced Jira+Confluence with Notion.”
neutral · production · willsr · 2018-09-30 · source ↗ · wrong label?“We do it within slack but also in things like jira. This way that 20 min chat doesn't get lost, it becomes meta/spec.”
neutral · production · social_quotient · 2018-08-23 · source ↗ · wrong label?“We run the Atlassian products Jira, Confluence and Crucible and soon Bitbucket on premise.”
neutral · production · __mp · 2018-07-26 · source ↗ · wrong label?“the architect specs these out separately using either a checklist or a functional spec which is then broken down into JIRA tickets.”
neutral · production · ian0 · 2018-07-02 · source ↗ · wrong label?“We self host JIRA, Jenkins, our own backoffice and other stuff on a small instance.”
neutral · production · danieka · 2017-11-29 · source ↗ · wrong label?“Before we switched to JIRA for issue tracking at $dayjob”
neutral · production · jamie_ca · 2017-11-20 · source ↗ · wrong label?“we've switched from an internal Jira to a public waffle.io backlog”
neutral · production · Sir_Cmpwn · 2016-06-16 · source ↗ · wrong label?“we switched to hosted Confluence, JIRA, BitBucket/git.”
neutral · production · nwatson · 2015-09-27 · source ↗ · wrong label?“We run most of the Atlassian products internally.”
neutral · production · adpd · 2015-07-13 · source ↗ · wrong label?“we use Jira and Kanban methodology.”
neutral · production · DigitalSea · 2014-12-12 · source ↗ · wrong label?“We also use Atlassian Stash and JIRA for a client project”
neutral · production · hypr_geek · 2014-04-22 · source ↗ · wrong label?“JIRA - issue tracking and feature management”
neutral · production · AH4oFVbPT4f8 · 2013-12-14 · source ↗ · wrong label?“moved to mercurial+JIRA, have Eclipse on more workstations than visual studio”
neutral · production · meaty · 2012-12-08 · source ↗ · wrong label?