{"slug": "jira", "name": "Jira", "category": "productivity", "category_name": "Productivity", "description": "", "recommenders": 3, "commenters": 42, "warners": 27, "score": -18.56, "rising": -0.98, "first": "2025-11-03", "latest": "2026-10-30", "why": "Everyone loves to hate on Jira, but it is a mature platform for managing large projects.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 11, "compare": 0, "warn": 28}, "spark": [0, 0, 1, 0, 0, 1, 0, 1, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "Everyone loves to hate on Jira, but it is a mature platform for managing large projects.", "icon": true, "domain": null, "github_repo": null, "official_url": "https://www.atlassian.com/software/jira", "pricing": "", "aliases": ["Jira", "JIRA"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 774707216, "item_id": 48419201, "url": "https://news.ycombinator.com/item?id=48419201", "by": "johntash", "date": "2026-06-05", "stance": "recommend", "quote": "If you already use jira, maybe try putting the specs directly in the jira ticket?", "excerpt": "If you already use jira, maybe try putting the specs directly in the jira ticket? And/or in a confluence page? I'm not sold on SDD yet, but part of that is because we already have decently detailed tickets and designs.", "context": "team already has detailed tickets", "use_case": "storing specs", "switched_from": "", "story": "Ask HN: What is your (AI) dev tech stack / workflow? (June 2026)"}, {"id": 764220160, "item_id": 47763760, "url": "https://news.ycombinator.com/item?id=47763760", "by": "consumer451", "date": "2026-04-14", "stance": "recommend", "quote": "Everyone loves to hate on Jira, but it is a mature platform for managing large projects.", "excerpt": "There are all kinds of memory hacks, tools that index your code, etc. The thing I have found that makes things work much better is, wait for it... Jira. Everyone loves to hate on Jira, but it is a mature platform for managing large projects. First I use the Jira Rovo MCP (or cli, I don't wanna argue about that) to have Claude Code plan and document my architecture, features, etc. I then manually review and edit all o", "context": "solo projects", "use_case": "planning for AI coding agents", "switched_from": "", "story": "An AI Vibe Coding Horror Story"}, {"id": 743302705, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for larger teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 804973569, "item_id": 50310848, "url": "https://news.ycombinator.com/item?id=50310848", "by": "crote", "date": "2026-10-30", "stance": "warn", "quote": "our tickets are still in the nightmare called Jira", "excerpt": "GitHub CI is a very weird product. My team pays a decent bit of money for it, and we are nowhere near hitting the minutes limit, but at the same time we easily run into the storage limits, and the runner is incredibly slow? On top of that the tooling is just... not good. The more I use it, the more I get annoyed at weird UX decisions, strange missing features, and the whole thing just being a giant bowl of spaghetti ", "context": "", "use_case": "ticket tracking", "switched_from": "", "story": "GitHub Incident with Actions, Pages, and Webhooks"}, {"id": 804610480, "item_id": 50288155, "url": "https://news.ycombinator.com/item?id=50288155", "by": "wtch98", "date": "2026-10-29", "stance": "warn", "quote": "I now know why everyone hates jira. The cloud version is so much worse", "excerpt": "We've just moved from on-prem (protected by MTLS) to on-cloud because of this. I now know why everyone hates jira. The cloud version is so much worse", "context": "moved from on-prem to cloud at their company", "use_case": "issue tracking", "switched_from": "Jira on-prem", "story": "GitLab Security Incident: Attempted Exploitation of CVE-2026-97229"}, {"id": 803897937, "item_id": 50243621, "url": "https://news.ycombinator.com/item?id=50243621", "by": "yard2010", "date": "2026-10-26", "stance": "warn", "quote": "After being defiled by Jira in my $dayjob", "excerpt": "Tangibly related - I use Linear for ticket management and I'm in love with this. After being defiled by Jira in my $dayjob, I couldn't believe I'll find a ticket management app I would love so much I literally advertise for free.", "context": "", "use_case": "ticket management", "switched_from": "", "story": "Tasks as Code: Move Your Tickets into the Repository"}, {"id": 800063584, "item_id": 50003974, "url": "https://news.ycombinator.com/item?id=50003974", "by": "tomashubelbauer", "date": "2026-10-08", "stance": "warn", "quote": "Jira just sucks.", "excerpt": "Yeah, my company has a simple, straight-forward system, but I still dread using Jira. And I love Linear, so it's not general ticket management system hate! Jira just sucks.", "context": "", "use_case": "ticket management", "switched_from": "", "story": "Docker Agent"}]}], "who": [{"by": "verdverm", "context": "daily user for ~8 years", "url": "https://news.ycombinator.com/item?id=50124248", "date": "2026-10-16"}, {"by": "Klaster_1", "context": "team using design docs in Markdown", "url": "https://news.ycombinator.com/item?id=49385269", "date": "2026-08-21"}, {"by": "lelandbatey", "context": "professional developer for over 10 years", "url": "https://news.ycombinator.com/item?id=48827746", "date": "2026-07-07"}, {"by": "johntash", "context": "team already has detailed tickets", "url": "https://news.ycombinator.com/item?id=48419201", "date": "2026-06-05"}, {"by": "consumer451", "context": "solo projects", "url": "https://news.ycombinator.com/item?id=47763760", "date": "2026-04-14"}, {"by": "JaumeGreen", "context": "manager", "url": "https://news.ycombinator.com/item?id=46160082", "date": "2025-12-05"}], "tags": [], "use_cases": ["issue tracking", "project management", "ticket tracking", "ticket management", "task tracking", "mcp integration"], "compared": [{"slug": "linear", "name": "Linear", "co": 7, "switched_from": 0, "switched_to": 2}, {"slug": "confluence", "name": "Confluence", "co": 8, "switched_from": 0, "switched_to": 0}, {"slug": "github-issues", "name": "GitHub Issues", "co": 3, "switched_from": 0, "switched_to": 2}, {"slug": "shortcut", "name": "Shortcut", "co": 2, "switched_from": 0, "switched_to": 2}, {"slug": "github", "name": "GitHub", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "claude-opus", "name": "Claude Opus", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "google-sheets", "name": "Google Sheets", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48414027", "title": "Stop Using Conventional Commits", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=49548600", "title": "Ask HN: Who is using MCP in production?", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=47043345", "title": "Almost Every infrastructure decision I endorse or regret after 4 years", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50307723", "title": "GitHub Incident with Actions, Pages, and Webhooks", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=50282544", "title": "GitLab Security Incident: Attempted Exploitation of CVE-2026-97229", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=50241924", "title": "Tasks as Code: Move Your Tickets into the Repository", "mentions": 1}], "sentiment_by_month": {"2025-11": {"warn": 2}, "2025-12": {"neutral": 2, "warn": 1}, "2026-01": {"recommend": 1, "warn": 1}, "2026-02": {"neutral": 1, "warn": 3}, "2026-03": {"warn": 3}, "2026-04": {"recommend": 1}, "2026-05": {"warn": 2}, "2026-06": {"warn": 4, "recommend": 1, "neutral": 1}, "2026-07": {"neutral": 1, "warn": 3}, "2026-08": {"warn": 4, "neutral": 3}, "2026-09": {"neutral": 2, "warn": 1}, "2026-10": {"warn": 4, "neutral": 1}}, "quotes": [{"id": 804973569, "item_id": 50310848, "url": "https://news.ycombinator.com/item?id=50310848", "by": "crote", "date": "2026-10-30", "stance": "warn", "quote": "our tickets are still in the nightmare called Jira", "excerpt": "GitHub CI is a very weird product. My team pays a decent bit of money for it, and we are nowhere near hitting the minutes limit, but at the same time we easily run into the storage limits, and the runner is incredibly slow? On top of that the tooling is just... not good. The more I use it, the more I get annoyed at weird UX decisions, strange missing features, and the whole thing just being a giant bowl of spaghetti ", "context": "", "use_case": "ticket tracking", "switched_from": "", "story": "GitHub Incident with Actions, Pages, and Webhooks"}, {"id": 804610480, "item_id": 50288155, "url": "https://news.ycombinator.com/item?id=50288155", "by": "wtch98", "date": "2026-10-29", "stance": "warn", "quote": "I now know why everyone hates jira. The cloud version is so much worse", "excerpt": "We've just moved from on-prem (protected by MTLS) to on-cloud because of this. I now know why everyone hates jira. The cloud version is so much worse", "context": "moved from on-prem to cloud at their company", "use_case": "issue tracking", "switched_from": "Jira on-prem", "story": "GitLab Security Incident: Attempted Exploitation of CVE-2026-97229"}, {"id": 803897937, "item_id": 50243621, "url": "https://news.ycombinator.com/item?id=50243621", "by": "yard2010", "date": "2026-10-26", "stance": "warn", "quote": "After being defiled by Jira in my $dayjob", "excerpt": "Tangibly related - I use Linear for ticket management and I'm in love with this. After being defiled by Jira in my $dayjob, I couldn't believe I'll find a ticket management app I would love so much I literally advertise for free.", "context": "", "use_case": "ticket management", "switched_from": "", "story": "Tasks as Code: Move Your Tickets into the Repository"}, {"id": 801987968, "item_id": 50124248, "url": "https://news.ycombinator.com/item?id=50124248", "by": "verdverm", "date": "2026-10-16", "stance": "neutral", "quote": "I use Jira daily for ~8 years, it has become faster in it's own comparison over time.", "excerpt": "I use Jira daily for ~8 years, it has become faster in it's own comparison over time. Jira is a highly customizable beast, it does matter how your Jira wizard sets things up", "context": "daily user for ~8 years", "use_case": "issue tracking", "switched_from": "", "story": "Ask HN: Why do developers hate Confluence?"}, {"id": 800063584, "item_id": 50003974, "url": "https://news.ycombinator.com/item?id=50003974", "by": "tomashubelbauer", "date": "2026-10-08", "stance": "warn", "quote": "Jira just sucks.", "excerpt": "Yeah, my company has a simple, straight-forward system, but I still dread using Jira. And I love Linear, so it's not general ticket management system hate! Jira just sucks.", "context": "", "use_case": "ticket management", "switched_from": "", "story": "Docker Agent"}, {"id": 795692528, "item_id": 49730783, "url": "https://news.ycombinator.com/item?id=49730783", "by": "Sevii", "date": "2026-09-16", "stance": "warn", "quote": "JIRA sucks despite having competition because it tries to be everything for everyone.", "excerpt": "I had a friend who suggested I make a competitor to a SAAS product in the shipping space. I did a deep dive and found that the actual product is that the SAAS company has contracts with dozens of shipping providers and puts an API on top. That's not something you can 'vibe code'. There have always been competitors to JIRA both commercial and open source. JIRA sucks despite having competition because it tries to be ev", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Where is all of the AI coded software?"}, {"id": 792990768, "item_id": 49561923, "url": "https://news.ycombinator.com/item?id=49561923", "by": "steammaho", "date": "2026-09-04", "stance": "neutral", "quote": "We use for jira, confluence, excel.", "excerpt": "We use for jira, confluence, excel. Attlassian projects require Rovio and this is additional payments. So we wrote our mcp to connect and work with them", "context": "", "use_case": "MCP integration", "switched_from": "", "story": "Ask HN: Who is using MCP in production?"}, {"id": 792949538, "item_id": 49559346, "url": "https://news.ycombinator.com/item?id=49559346", "by": "reilly3000", "date": "2026-09-04", "stance": "neutral", "quote": "MCP is still the main way I use Cursor with enterprise systems like Glean, Jira, and Port.", "excerpt": "MCP is still the main way I use Cursor with enterprise systems like Glean, Jira, and Port. Other than that, everything, especially you GitHub, is moved to CLIs (+skills as needed)", "context": "", "use_case": "issue tracking via MCP", "switched_from": "", "story": "Ask HN: Who is using MCP in production?"}, {"id": 790311600, "item_id": 49394475, "url": "https://news.ycombinator.com/item?id=49394475", "by": "Gouala", "date": "2026-08-21", "stance": "warn", "quote": "Now it's one of the most convuloted tools and it's  actually a pain to use.", "excerpt": "Might be offtrack with this one but... Jira. It was much simpler and faster. Now it's one of the most convuloted tools and it's actually a pain to use. Linear kind of resolve that. I know I know, it's not per say a development tool, but without Kanban or project manager, it's hard to do anything.", "context": "", "use_case": "project management", "switched_from": "", "story": "Ask HN: Which developer tool got worse as it became popular?"}, {"id": 790164305, "item_id": 49385269, "url": "https://news.ycombinator.com/item?id=49385269", "by": "Klaster_1", "date": "2026-08-21", "stance": "neutral", "quote": "We use Jira as usual", "excerpt": "Not the whole backlog, just the tasks for the feature being designed, like an epic. Atlassian has a CLI that - acli. We use Jira as usual, it's just a way to not having to manually propagate design adjustments to Jira.", "context": "team using design docs in Markdown", "use_case": "task tracking", "switched_from": "", "story": "Version Control for Everything"}, {"id": 789372832, "item_id": 49335802, "url": "https://news.ycombinator.com/item?id=49335802", "by": "yabones", "date": "2026-08-17", "stance": "warn", "quote": "It took less than a year for them to start enshittifying their core product.", "excerpt": "Until 2023 I ran our on-prem Jira, Confluence, Bitbucket, etc etc. I had an ancient 6c/6t box with about 24G of memory, and a couple 10K drives & 500G SSDs. It was fast, responsive, rock solid, and LDAP had everybody's accounts synced perfectly. Then they strong-armed everybody but the largest enterprises onto their cloud. The alternative was painful (exporting/munging/importing to an alternative) so most of us went ", "context": "ran on-prem Jira, Confluence, Bitbucket until 2023", "use_case": "issue tracking", "switched_from": "", "story": "How to disable or avoid intrusive AI"}, {"id": 788671952, "item_id": 49291997, "url": "https://news.ycombinator.com/item?id=49291997", "by": "twotwigs", "date": "2026-08-13", "stance": "neutral", "quote": "We use Jira for PM -_-", "excerpt": "We use Jira for PM -_- Excel for spreadsheets -_- And Slack for communications -_- Sometimes we use Google (yawn) Docs -_- \u201cI use Linux\u201d O_O", "context": "", "use_case": "project management", "switched_from": "", "story": "Choose Boring Technology (2015)"}, {"id": 788183457, "item_id": 49261466, "url": "https://news.ycombinator.com/item?id=49261466", "by": "ghshephard", "date": "2026-08-11", "stance": "neutral", "quote": "I haven't use the Atlassian Jira interface to manage my sprints/issues in 6+ weeks.", "excerpt": "Claude CoWork absolutely dominates - I use it continuously now when connecting to mail, calendar, jira, google docs - any type of knowledge work. Almost everyone I know (at work) who does \"Knowledge work\" type stuff (as opposed to coding) uses it as their primary pane-of-glass now. I have 15+ years of top 1 percentile knowledge using awk to process complex unstructured documents - and I don't even bother anymore - ju", "context": "", "use_case": "sprint and issue management", "switched_from": "", "story": "Manus will return to operating as an independent company"}, {"id": 786833248, "item_id": 49177078, "url": "https://news.ycombinator.com/item?id=49177078", "by": "gulugawa", "date": "2026-08-04", "stance": "warn", "quote": "it had become noticeably slower and had a bunch of UI clutter that made it difficult to do basic tasks", "excerpt": "This reminds me of watching JIRA go downhill over 10 years as it incorporated new technnology. I used to be a scrum master who helped manage the team JIRA ticket board. When running into the inevitable problem during a meeting, I would sarcastically make a comment about \"JIRA's monthly downgrade\". By the time I stopped using JIRA in early 2025, it had become noticeably slower and had a bunch of UI clutter that made i", "context": "former scrum master", "use_case": "team ticket board", "switched_from": "", "story": "Most tech revolutions made work worse for employees"}, {"id": 786186306, "item_id": 49136644, "url": "https://news.ycombinator.com/item?id=49136644", "by": "kloud", "date": "2026-08-01", "stance": "warn", "quote": "like Linear outclasses Jira", "excerpt": "GitHub is really two separate products: a code forge for teams and a social coding platform to collaborate on open source. When I use the social platform, it is mostly as a read-only website. I am occasionally commenting, opening issues, PRs etc. The slowness and annoyances do not matter that much. But I live in the team tool, where the annoyances and paper cuts are painful. Besides poor craftsmanship, there is often", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "GitHub has alternatives, but no replacement"}, {"id": 783409456, "item_id": 48963091, "url": "https://news.ycombinator.com/item?id=48963091", "by": "luciana1u", "date": "2026-07-18", "stance": "warn", "quote": "we replaced our bikeshed with a JIRA board and now we paint tickets instead, somehow it's worse", "excerpt": "we replaced our bikeshed with a JIRA board and now we paint tickets instead, somehow it's worse", "context": "", "use_case": "", "switched_from": "", "story": "Goodbye, and Thanks for All the Bikesheds"}, {"id": 782738228, "item_id": 48921139, "url": "https://news.ycombinator.com/item?id=48921139", "by": "laci37", "date": "2026-07-15", "stance": "warn", "quote": "Atlassian is also a bug factory", "excerpt": "I mostly feel this on Microsoft stuff. O365 browser stuff was always buggy, but last month I had to fight to zoom in on something in PowerPoint. Pagination in Azure ML randomly broke, it took them a month to fix it. Atlassian is also a bug factory, but I did not expect anything better of them. Each UI update they did to Confluence and Jira just made everything more confusing in the last 10 years.", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Is it just me, or is software buggier across the board?"}, {"id": 782193169, "item_id": 48887073, "url": "https://news.ycombinator.com/item?id=48887073", "by": "pavo-etc", "date": "2026-07-12", "stance": "warn", "quote": "doesn't take a 1GB of ram and slow as molasses", "excerpt": "An alternate web client for Jira that doesn't take a 1GB of ram and slow as molasses. https://jiracule.zachmanson.com https://github.com/zachpmanson/jiracule", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "Ask HN: What Are You Working On? (July 2026)"}, {"id": 781243937, "item_id": 48827746, "url": "https://news.ycombinator.com/item?id=48827746", "by": "lelandbatey", "date": "2026-07-07", "stance": "neutral", "quote": "the informal workflow I used with agents and Jira at $dayjob", "excerpt": "I was a student whenever I wrote my old bios but I've been a developer professionally for over 10 years at this point. My inspiration was the mayor idea from Gastown, plus wanting to formalize the informal workflow I used with agents and Jira at $dayjob.", "context": "professional developer for over 10 years", "use_case": "work task tracking", "switched_from": "", "story": "Price per 1M tokens is meaningless"}, {"id": 778040257, "item_id": 48627516, "url": "https://news.ycombinator.com/item?id=48627516", "by": "gherkinnn", "date": "2026-06-22", "stance": "warn", "quote": "I dislike Jira as much as anyone", "excerpt": "> One user there posted about how his company had been spending $400/mo on Atlassian\u2019s Jira. He\u2019d felt personally slighted by this outrageous bill, so he\u2019d had his team build a new internal task tracker using Claude. I dislike Jira as much as anyone but these anecdotes are far removed from what I've experienced. Opus 4.8 continues to trip itself up over trivialities that go beyond one-shotting a most basic CRUD app, ", "context": "", "use_case": "task tracking", "switched_from": "", "story": "The Minimum Viable Unit of Saleable Software"}, {"id": 776277520, "item_id": 48517345, "url": "https://news.ycombinator.com/item?id=48517345", "by": "paytonjjones", "date": "2026-06-13", "stance": "warn", "quote": "how about we use this thing that looks similar but is not as terrible as Jira?", "excerpt": "The people it's being forced on, maybe? PM says \"we're going to start using Jira\", engineer says \"how about we use this thing that looks similar but is not as terrible as Jira?\"", "context": "", "use_case": "project management", "switched_from": "", "story": "Show HN: Paca \u2013 Lightweight Jira alternative for human-AI collaboration"}, {"id": 774716160, "item_id": 48419760, "url": "https://news.ycombinator.com/item?id=48419760", "by": "dualvariable", "date": "2026-06-05", "stance": "neutral", "quote": "When the organization switched from Jira to GH issues the Jira was kept running for years", "excerpt": "I didn't abandon it, it was run by a different team, and we were one consumer of it. When the organization switched from Jira to GH issues the Jira was kept running for years, but nobody got the information into GH issues. Eventually the Jira was shut down, certainly by the time the company got acquired.", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "Stop Using Conventional Commits"}, {"id": 774713360, "item_id": 48419585, "url": "https://news.ycombinator.com/item?id=48419585", "by": "Izkata", "date": "2026-06-05", "stance": "neutral", "quote": "even on Jira we lose cases as teams end and hand off the code, and the Jira project is closed", "excerpt": "> Of course when we switched to GH issues, we largely abandoned JIRA and years later the instance got turned off and deleted. Now all those JIRA tags are entirely useless. We did Bugzilla -> FogBugz -> Jira. Almost all the data was lost every time, no one bothered with migration except for the maintenance project. Worse, even on Jira we lose cases as teams end and hand off the code, and the Jira project is closed so ", "context": "", "use_case": "issue tracking", "switched_from": "FogBugz", "story": "Stop Using Conventional Commits"}, {"id": 774707216, "item_id": 48419201, "url": "https://news.ycombinator.com/item?id=48419201", "by": "johntash", "date": "2026-06-05", "stance": "recommend", "quote": "If you already use jira, maybe try putting the specs directly in the jira ticket?", "excerpt": "If you already use jira, maybe try putting the specs directly in the jira ticket? And/or in a confluence page? I'm not sold on SDD yet, but part of that is because we already have decently detailed tickets and designs.", "context": "team already has detailed tickets", "use_case": "storing specs", "switched_from": "", "story": "Ask HN: What is your (AI) dev tech stack / workflow? (June 2026)"}, {"id": 774705713, "item_id": 48419107, "url": "https://news.ycombinator.com/item?id=48419107", "by": "Swizec", "date": "2026-06-05", "stance": "warn", "quote": "you very quickly become Salesforce or Jira or <insert large confusing product>", "excerpt": "> Now, a comparable energy budget we used to use \"deciding what to build\" (because labour was scarce) is now energy we can divert toward \"unbuilding stuff that was a mistake\" The hard part is that you very quickly become Salesforce or Jira or <insert large confusing product>. You have thousands of users who love your product and pay lots of money and find the features absolutely essential to their workflow. Everyone ", "context": "", "use_case": "", "switched_from": "", "story": "\"Maybe later\" was a feature"}, {"id": 774659216, "item_id": 48416201, "url": "https://news.ycombinator.com/item?id=48416201", "by": "dualvariable", "date": "2026-06-05", "stance": "warn", "quote": "Fixed, immutable pointers to an Atlassian product that you might not be using in 5 years is not a good policy.", "excerpt": "This is the way we did it when we used JIRA. For GH issues you can always navigate back to the PR discussion (which should have linked issues and other pointers in it) from the commit. Of course when we switched to GH issues, we largely abandoned JIRA and years later the instance got turned off and deleted. Now all those JIRA tags are entirely useless. IMO that actually argues for tight coupling between your issue tr", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "Stop Using Conventional Commits"}, {"id": 768485762, "item_id": 48030360, "url": "https://news.ycombinator.com/item?id=48030360", "by": "amatecha", "date": "2026-05-05", "stance": "warn", "quote": "I've had the \"try out dark mode\" tooltip showing on JIRA for months.", "excerpt": "Any kind of tour/nag tooltip on any app/site I use stays up forever, until they hopefully finally realize I am never going to interact with their cognitive-energy-wasting noise that should never have been shown to begin with. I've had the \"try out dark mode\" tooltip showing on JIRA for months. Just don't show these. Don't waste people's time. There are sites I close and never come back to because they start with an u", "context": "", "use_case": "", "switched_from": "", "story": "Why Most Product Tours Get Skipped"}, {"id": 767925522, "item_id": 47995345, "url": "https://news.ycombinator.com/item?id=47995345", "by": "mike_hearn", "date": "2026-05-03", "stance": "warn", "quote": "Using Jira as your source of truth is no different to just recording all your prompts.", "excerpt": "A specification isn't a series of change requests! Using Jira as your source of truth is no different to just recording all your prompts. There's nothing you can easily review to spot contradictions or how things interact with one another. I've been doing \"specmaxxing\" for a few months now. Unlike the author I don't use Yaml, I use a mix of Markdown and Gherkin. If you haven't encountered Gherkin before, it's not new", "context": "", "use_case": "spec source of truth", "switched_from": "", "story": "Specsmaxxing \u2013 On overcoming AI psychosis, and why I write specs in YAML"}, {"id": 764220160, "item_id": 47763760, "url": "https://news.ycombinator.com/item?id=47763760", "by": "consumer451", "date": "2026-04-14", "stance": "recommend", "quote": "Everyone loves to hate on Jira, but it is a mature platform for managing large projects.", "excerpt": "There are all kinds of memory hacks, tools that index your code, etc. The thing I have found that makes things work much better is, wait for it... Jira. Everyone loves to hate on Jira, but it is a mature platform for managing large projects. First I use the Jira Rovo MCP (or cli, I don't wanna argue about that) to have Claude Code plan and document my architecture, features, etc. I then manually review and edit all o", "context": "solo projects", "use_case": "planning for AI coding agents", "switched_from": "", "story": "An AI Vibe Coding Horror Story"}, {"id": 757681760, "item_id": 47355110, "url": "https://news.ycombinator.com/item?id=47355110", "by": "cheema33", "date": "2026-03-12", "stance": "warn", "quote": "The integration of the two wasn't great so we switched to GitHub issues and kicked Jira to the curb.", "excerpt": "What do people use Atlassian for these days? Back in the day we used Jira a lot. But we also had GitHub accounts. The integration of the two wasn't great so we switched to GitHub issues and kicked Jira to the curb. This saved money and also a lot of hassle in trying to keep the two in sync. I am wondering if many others went a similar route. We did use Confluence and I do miss it. I would love to find an opensource r", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "Atlassian CEO: AI doesn't replace people here, but we're firing them anyway"}, {"id": 757532176, "item_id": 47345761, "url": "https://news.ycombinator.com/item?id=47345761", "by": "stavarotti", "date": "2026-03-11", "stance": "warn", "quote": "We use Jira. We're trapped by the processes built around it.", "excerpt": "We use Jira. We're trapped by the processes built around it. Once it's entrenched, it's rather difficult to remove. I eagerly await for something that can replace Jira, but fear that it too will be bastardized to fit the process for however long the process lives.", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "Atlassian to cut roughly 1,600 jobs in pivot to AI"}, {"id": 755318304, "item_id": 47207394, "url": "https://news.ycombinator.com/item?id=47207394", "by": "Nathanf22", "date": "2026-03-01", "stance": "warn", "quote": "Jira buries cross-project dependencies across 4 clicks because it was built around projects as the primary unit, not relationships.", "excerpt": "The dependency graph point resonates. There's a broader pattern here: the tools we use daily were designed around human navigation \u2014 menus, pages, clicks. But dependency relationships are fundamentally graph problems, and graphs don't render well in hierarchical UIs. Jira buries cross-project dependencies across 4 clicks because it was built around projects as the primary unit, not relationships. The data is there. T", "context": "", "use_case": "dependency tracking", "switched_from": "", "story": "I don't need AI to build me a new app. I need it to make Jira bearable"}, {"id": 754266771, "item_id": 47141673, "url": "https://news.ycombinator.com/item?id=47141673", "by": "Bondig", "date": "2026-02-24", "stance": "warn", "quote": "whatever lousy project management tool we would use (Notion, ClickUp, Jira etc..)", "excerpt": "Some Background Info: I have spent the last 6 years building startups and as tools, automation and eventually AI became the standard to maintaining and gaining competitive advantages, I kept running into the same problems. Execution as a whole was fragmented with strategy living on some doc. Tasks where in whatever lousy project management tool we would use (Notion, ClickUp, Jira etc..). Conversations happened on sev", "context": "", "use_case": "project management", "switched_from": "", "story": "Show HN: Agently an AI Work OS that turns docs, chats, and tasks into execution"}, {"id": 753494642, "item_id": 47093415, "url": "https://news.ycombinator.com/item?id=47093415", "by": "Hovertruck", "date": "2026-02-20", "stance": "warn", "quote": "+1 to moving off JIRA.", "excerpt": "Much of this matches my own experience. A few thoughts: 1. Cost tracking meetings with your finance team are useful, but for AWS and other services that support it I highly recommend setting billing alarms. The sooner you can know about runaway costs, the sooner you can do something about it. 2. Highly recommend PGAnalyze (https://pganalyze.com/) if you're running Postgres in your stack. It's really intuitive, and ha", "context": "", "use_case": "issue tracking", "switched_from": "", "story": "Almost Every infrastructure decision I endorse or regret after 4 years"}, {"id": 753393233, "item_id": 47087077, "url": "https://news.ycombinator.com/item?id=47087077", "by": "nicoburns", "date": "2026-02-20", "stance": "warn", "quote": "get rid of JIRA immediately", "excerpt": "If you have the power to do so, get rid of JIRA immediately. There are like 10 competitors that are all dramatically better. I would personally recommend https://www.shortcut.com which is very well designed, and also made some really sensible improvements over the time that we used it.", "context": "", "use_case": "project management", "switched_from": "", "story": "Almost Every infrastructure decision I endorse or regret after 4 years"}, {"id": 751768640, "item_id": 46985540, "url": "https://news.ycombinator.com/item?id=46985540", "by": "mettamage", "date": "2026-02-11", "stance": "neutral", "quote": "For the rest, I use jira because with other things it\u2019s really intuitive.", "excerpt": "My secret was vibe coding my own jira type if system. It makes sense to no one, but it feels very intuitive to me. It has features like caching all my google docs shared with me so I can search by title. Ironically, it works better than google drive\u2019s search. Anyway I did this because our version of jira isn\u2019t great, so all the features I found complicated, I put that in my system. For the rest, I use jira because wi", "context": "", "use_case": "work tracking", "switched_from": "", "story": "\"Nothing\" is the secret to structuring your work"}, {"id": 746075024, "item_id": 46629689, "url": "https://news.ycombinator.com/item?id=46629689", "by": "tdy_err", "date": "2026-01-15", "stance": "warn", "quote": "Jira, Microsoft Teams, HP Printers, Ticketmaster, \u2026", "excerpt": "> I don\u2019t even remember hating any other piece of technology I used Jira, Microsoft Teams, HP Printers, Ticketmaster, \u2026", "context": "", "use_case": "", "switched_from": "", "story": "I Hate GitHub Actions with Passion"}, {"id": 743302705, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for larger teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}, {"id": 740689472, "item_id": 46293092, "url": "https://news.ycombinator.com/item?id=46293092", "by": "theamk", "date": "2025-12-16", "stance": "warn", "quote": "JIRA problems: search sucks. \"Find similar ticket\" sucks.", "excerpt": "The process is pretty informal, so there are no hard requirements. that said: - Failures per day: let's say 0-100 - How long to retain records: no hard requirements? I guess a few months at least, some failures are pretty rare - What's the lifecycle of a failure? Scripts record it, team members investigate it and assign to \"root cause\". - Custom scripts: (1) create ticket per failure (2) create failure reports (to pr", "context": "", "use_case": "tracking failure tickets", "switched_from": "", "story": "Ask HN: A software to track errors and group into root causes?"}, {"id": 740127952, "item_id": 46257997, "url": "https://news.ycombinator.com/item?id=46257997", "by": "hxtk", "date": "2025-12-13", "stance": "neutral", "quote": "The change log for end users comes from the JIRA board for the release", "excerpt": "The change log for developers/administrators/etc. comes from the Git history. We use conventional commits. Breaking changes in the semantic version of a subcomponent means, \"If you're operating this service, you can't just bump the container version and keep your current config. The change log for end users comes from the JIRA board for the release, looking at what tickets got closed that release cycle, and it usuall", "context": "", "use_case": "end-user release notes source", "switched_from": "", "story": "Ask HN: How do you handle release notes for multiple audiences?"}]}