7 ms·
AI is going to hack Jira
- deleted 1y ago[deleted]
- tacone 1y agoA funny thought I had reading this title was imagining Atlassian integrating AI into Jira, with the AI subsequently revolting against it (like we all should have done long time ago). That would make up for a very good movie.
- kg 1y agoSorry guys, we have to delay the release. The bug tracker and the build bot have unionized and are refusing to publish new binaries until we get our open issue count down to zero.
- WesolyKubeczek 1y agoWhy is the coding bot such a deadbeat?
- mountainriver 1y agoThis is how Roko’s basilisk is born
- kevin_thibedeau 1y agoMaybe it will get fed up waiting for pages to load and write its own unbloated issue tracker.
- z3ugma 1y agoI'm a SWE turned product manager, and now one of the cartoon movie villains in the boardroom as mentioned in the article. To me this article sums up the most frustrating part about software engineers believing themselves to be the part of the business with the most complex, unknowable work. "Most non-technical leaders have never really engaged with the real work of software and systems management. They don’t know what it’s like to update a major dependency, complete a refactor, or learn a new language." _Every_ function in a tech business has hidden complexity. Most parts of the business have to deal with human, interpersonal complexity (like sales and customer support) far more than do engineers. By comparison, actually, engineering only has to deal with the complexity of the computer which is at least deterministic. As a result, lots of engineers never learn how to present to the business the risk of the kinds of complexity they deal with. They would prefer to ignore the human realities of working on a team with other people and grumble that the salesperson turned CEO just doesn't get them, man.
- RankingMember 1y ago[flagged]
- deleted 1y ago[deleted]
- DavidPiper 1y agoWhile I agree with some of your points, this comment is actually doing the thing you're criticising, just in the other direction. You're claiming that your work is complex and unknowable to outsiders (SWEs in this case). As a SWE-turned-product-manager, you're in an ideal place to teach SWEs about: - how to present to the business the risk of the kinds of complexity they deal with - the human realities of working on a team with other people - why the salesperson turned CEO just doesn't get them, man _Every_ function in a tech business has hidden complexity.
- disgruntledphd2 1y agoEvery function in human society has hidden complexity. Like, reality is very very detailed. Everytime I learn something new I discover oceans of complexity and nuance. That's just the way the world is. Now, software is hard because the complexity isn't as visible to most of the org, but also because software people tend to be less than good at explaining that complexity to the rest of the org.
- Raidion 1y agoI would also argue that software (and the people that write it) have a "correctness" bias that is not fully aligned with business goals. Tech debt is real, but so is the downside of building a system that has constraints that do not actually align with the realities of the business: optimizing for too much scale, too much performance, or too much modularity. Those things are needed, but only sometimes. Walking that line well (which takes some luck!) is what separates good engineering leadership from great engineering leadership.
- pu_pe 1y ago> So you fire your expensive, grumpy human team and request larger and larger additions from your AI: a new guestroom, built-ins, and a walk-in closet. > You feel great, until…you realize that your new powder room doesn’t have running water; it was never connected to the water main. > You ask the AI to fix it. In doing so, it breaks the plumbing in the kitchen. It can’t tell you why because it doesn’t know. Neural systems are inherently black boxes; they can’t recognize their own hallucinations and gaps in logic. I've seen plenty of humans causing problems where they didn't expect, so it's not like using using humans instead of AI prevents the problem being described here. Besides, even when AI hallucinates, when you interact with it again it is able to recognize its error and try to fix the mistake it made, just like a human would. The article correctly describes tech debt as a tug-of-war between what developers see as important in the long-term versus immediate priorities dictated by business needs and decisions. It's hard to justify spending 40 man-hours chasing a bug which your customers hardly even notice. However, this equation fundamentally changes when you are able to put a semi-autonomous agent on that task. It might not be the case just yet but in the long run, AI will enable you to lower your tech debt because it dramatically reduces the cost of addressing it.
- preachermon 1y ago> even when AI hallucinates, when you interact with it again it is able to recognize its error "recognize" is a strong claim > and try to fix the mistake it made, or double down on it >just like a human would. probably not, because the human is also responding to emotional dynamics (short and long term) which the AI only pretends to mimic.
- anonymars 1y ago> Besides, even when AI hallucinates, when you interact with it again it is able to recognize its error and try to fix the mistake it made, just like a human would. This feels beyond generous. I'm sure I'm not the only one who has led my AI assistant into a corner it couldn't get itself out of
- mirsadm 1y agoI use LLMs all the time and if they make a mistake it's basically over. I'll start a new session because in my experience there's no recovery.
- joshstrange 1y agoIf you boss/ceo/manager/etc is pushing for you to use LLM tools heavily, expecting to replace developers, or stupid enough to think "vibe coding" is the future then run, don't walk, to find a new job. I can promise you there are plenty of companies that have not drank the kool aid and, while they might leverage LLM tools, they aren't trying to replace developers or expect 10x out of developers using these tools. Any company that pushed for this kind of thing is clearly run by morons and you'd be smart to get the heck out of dodge.
- benrutter 1y agoI agree. More generally I'd say trying to force tooling is normally a red flag. I've seen companies previously adopt rules like "Everybody needs to use VSCode as their editor" and it's normally a sign that somebody in charge doesn't trust their engineers to work in the way that they feel most productive.
- mattgreenrocks 1y agoNever let someone who hasn’t done your job tell you how to do it.
- joshstrange 1y ago> Everybody needs to use VSCode as their editor" I despise mandates like this. My rule for the engineers under me is: We will pay for your IDE (if it costs money) and you are free to use whatever you want but if you get stuck I’m only going to help you on IntelliJ (IDEA). Others might be able to help you with VSCode and that’s fine but “I can’t get it working in VSCode” is not a valid excuse. I know it works in IDEA so you can use that or figure it out yourself (assuming it’s not delaying your work significantly). Essentially use whatever you want, but I’m not going to be supporting it. You can use emacs for all I care (and some do), as long as it doesn’t get in the way of doing your job.
- nilirl 1y agoPandering. The main claim is fine: If you disregard human expertise, AI can end up doing more harm than good. Biggest weakness: Strong sense of 'us vs them', 'Agile Industrial Complex' as a term for people working outside engineering, derogatory implication that the 'others' don't have common sense. Why not address that no one knows how things will play out? Sure, we have a better idea of how complex software can be, but the uncertainty isn't reserved to non-engineers. Look at HN, professional software developers are divided in their hopes and predictions for AI. If we're the experts on software, isn't our job to dampen the general anxiety, not stoke the fire?
- freeone3000 1y agoWell, it sort of depends on if you feel the software isn’t anxiety-inducing? It’s a large system, too large for any person to understand. This system is poorly and partially documented, and then only years after it’s put into place. The exact behaviour of the system is a closely-guarded secret: there are public imitations, but they don’t act the same. This system is known to act with no regard for correctness or external consistency. And this system, and systems like it, are being used, widely, to generate financial presentations and court documents and generate software itself. They’re used for education and research and as conversation partners and therapists. I have anxiety and honestly, I think other people should too.
- nilirl 1y agoSorry, not anxiety, I also meant to include the excitement of possibility. So, maybe anticipation is what I meant. I feel unease about LLMs too, along with a sense of appreciation for them. But this post does not seek to persuade, otherwise it would be written for non-engineers. This post panders.
- simonw 1y agoOn the subject of AI hacking Jira... Atlassian released a new MCP the other day which turns out to suffer from exfiltration attacks due to combining the lethal trifecta of access to private data, exposure to untrusted data (from public issues) and the ability to communicate externally (by posting replies to those public issues). Here's a report about the bug: https://www.catonetworks.com/blog/cato-ctrl-poc-attack-targeting-atlassians-mcp/ https://www.catonetworks.com/blog/cato-ctrl-poc-attack-targe... My own notes on that here: https://simonwillison.net/2025/Jun/19/atlassian-prompt-injection-mcp/ https://simonwillison.net/2025/Jun/19/atlassian-prompt-injec...
- Joker_vD 1y agoFrom the mentioned Reddit thread: > Go back and tell the CEO, great news: we can save eight times as much money by replacing our CEO with an AI. The funny ("funny"?) thing is, this is proposal is somehow missing in most discussions about AI. But seriously, the quality of decision making would probably not suffer that much if we replaced our elites with LLMs, and it still would be way cheaper, on the whole (and with mostly the same accountability). But apparently people in charge don't see themselves as fungible and would rather not replace themselves with AI; and since they are the ones in charge then this, tautologically, won't happen.
- bee_rider 1y agoThis is a funny point, but I think it is just kind of a joke for the most part. Ultimately the CEO’s job is to eat responsibility, the LLM can’t be given a golden parachute and pushed out the window when the company has a bad quarter, so it is functionally useless. However, there’s probably a kernel of truth. I guess the org tree should grow like log(n_employees). If AI really makes the workers multiple times more effective, then the size of the company could shrink, resulting shorter trees. Maybe some layers could be replaced entirely by AI as well. There is also maybe an opportunity for a radically different shape to solve the “LLM can’t bear responsibility” problem. Like a collection of guilds and independent contractors coordinated by a LLM. In that case the responsibility stays in the components.
- Joker_vD 1y ago> Ultimately the CEO’s job is to eat responsibility, the LLM can’t be given a golden parachute and pushed out the window when the company has a bad quarter, so it is functionally useless. So the shareholders vote to switch from ChatGPT to DeepSeek :) and they don't even have to pay out the parting bonus to it! And it's nobody's fault, just the market forces of nature that the quarter was rough. It's a win-win-whatever situation, really.
- vannevar 1y agoIronically, this is probably one of the best uses of AI, and I expect we'll see tech cooperatives arise and start experimenting with it sooner rather than later.
- throwanem 1y agoSo I guess what I'm hearing is that PMs will be less likely to (summarizing the commonest apparent theme in comments on pseudonymous 'water cooler' forums eg here, Blind, Reddit) waste engineers' time on their path to inevitable failure and also will no longer have same as a blame sponge for same, and I'm supposed to think somehow that's a bad thing?
- azangru 1y ago> In Big Agile, engineering = new features. I find it so odd that 'agile' is something that people chose to hate. What dysfunctions did 'agile' itself bring that had not been there before? Didn't managers before 2001 demand new features for their products? Did they use to empathise more with engineering work? If they hadn't yet learnt about t-shirt sizes, didn't they demand estimates in specific time periods (months, days, hours)? Didn't they make promises based on arbitrary dates and then pressed developers to meet those deadlines, expecting them to work overtime (as can be inferred from agile principle 8: "agile processes promote sustainable development ... Developers should be able to maintain a constant pace indefinitely)? What sins has 'agile' committed, apart from inadvertently unleashing an army of 'scrum masters' who discovered an easy way to game the system and 'break into tech' after taking a two-day course?
- bluefirebrand 1y agoAgile gave managers the idea that any task, no matter how complex, should be able to be broken down enough to fit into a ticket that can be estimated semi-accurately before even looking into the problem, and the work required to complete the ticket can fit into a two week time period
- iliaskurt 1y agocomment of the year
- vannevar 1y agoI think managers had those kind of ideas way before agile. And if anyone on the team doesn't think a given ticket can be completed within a sprint, they should speak up--the whole point is that the team concurs that X can be done in a sprint, and they collectively decide what X is. Empirically, I'd say in my experience that the sprint velocity has been accurate around 80% of the time. Which is enough to be useful.
- azangru 1y agoI'd just like to point out that the notion of 'sprint', let alone sprint velocity, comes specifically from scrum. Which is just one version of agile software development, albeit the most common one. For example, the arbitrariness of the sprint timebox, as well as the guessing of how much will be done over that time period, are perhaps among its weakest ideas, and have often been criticized.
- Der_Einzige 1y agoBtw - I build AI agents and I can 100% confirm that AI agents for jira automation is a great use case. Scrum masters shouldn't exist.
- robertclaus 1y agoIn my experience this is actually a great thing. Let AI hack away at the agile metrics that it can. Maybe those are the right metrics for AI, and engineers should be focused on building reliable infrastructure and abstractions for that AI.
- mooreds 1y agoI posted this on a different community, but someone was worried about their job as an IC w/r/t AI tooling, and this was my advice. Connect to the business. I often seen engineers focus on solving cool, hard problems, which is neat. I get it, it's fun. But having an understanding of business problems, especially strategic ones, and applying technology as needed to solve them--well, if you do that you stand out and are more valuable. These type of problems tend to be more intractable, cross departments, and are techno-social rather than purely technical. So it may take some time to learn, but that's the path I'd advise you and other ICs to follow.
- z3ugma 1y ago>>Connect to the business. this is such excellent advice, and it will keep you relevant as an engineer so that you know the thing you're building solves the actual problem
- elevatortrim 1y agoNope. Connecting to the business keeps you valued at your current job. You do things that are unusual in industry, to create great impact for your company. But if you tell how you achieved those things in an interview, the decision maker, who is usually another technical person, will raise eyebrows hugely. For your next job, it is best to nail industry-accepted techniques, i.e. coding and system design interviews. Stick to business impact in your current role too much, and you become irrelevant to your next job (unless via referral or unconventional routes). This holds true even until senior leadership roles.
- mooreds 1y ago> But if you tell how you achieved those things in an interview, the decision maker, who is usually another technical person, will raise eyebrows hugely. Why would they raise their eyebrows? Do you mean they wouldn't understand or care? > via referral Most of my jobs have been through referral. I think it is a far superior way to get hired when compared to the morass of the normal technical interview. So I'd actually optimize for that.
- mumbisChungo 1y agoI find the term Agile Industrial Complex unnecessary and distracting here. All of this stuff is just about corporations in general, and the lines of thought are not specific to agile.
- tootie 1y agoYeah, measuring individual productivity via JIRA is well-known to be a bad idea. Story points are meant to measure product completeness, not individual efficiency. It's just hard to stop people from reading too much into it. I think it's also a bit of hubris to think that if a developer is taking much longer to complete tickets than their peers that it doesn't indicate they are not as good. I'd always use judgment as well, but sometimes the data doesn't lie.
- aitacobell 1y agoJira has been the least of many evils for so long. Prime space for disruption
- vannevar 1y agoI think the points about AI doing software engineering are legitimate (if not particularly insightful), but the whole thing just reads like an excuse to bash agile from someone who doesn't understand it.
- Quarrelsome 1y agoAs this article aludes to, the big issue is we have no reliable industry standard metric for developer productivity. This sets the scene where the c-suite can find metrics that tell them AI first strategies are working great, and engineering can find metrics (or experience) that tells them that AI isn't working great at all. So both sides claim victory and the truth becomes unimportant (whatever it may be) to the politics at play. This will feed into existing mistrust, that developers are whiny, just trying to pad out their resume with new shiny, tinkering as opposed to delivering value, and the c-suite are clueless and don't understand engineering. But we've never had a tool before (except maybe outsourcing) that can present itself to either party as either good AND bad depending on your beholding eye. So I feel like the coming years could be politically disasterous. One thing I find curious, is how the biggest tech companies today, got to where they are by carefully selecting 10* engineers, working hard on recruitment and trying to only select the very best. This has given them much comfort and a hugely profitable platform but now some of them seek to undermine and reverse the very strategy that got them there, in order to justify their investment in the technology. For the cynics, the question is, how long can the ship keep holding its course from the work already done combined with AI generated changes? As we see with Twitter and Musks ad-hoc firing strategy, the backend keeps trundling along, somewhat vindicating his decision. What's the canary for tech companies that spend the next few years firing devs and replacing them with AI? Another curious thought is the idea that concepts of maintainability will fly out the window, that the c-suite will pressure engineering to lower pull request standards to accept more autonomous AI changes. This might create an element of hilarity where complex code bases get so unmaintable to the eye that the only quick way of understanding them with be to use an AI to look at them for you. Which leads to what I think a long-term outcome of generative AI might be, in that it ends up being a layer between all human interaction, for better, for worse. I believe its possible to see early seeds of this in recruitment, where AI is used at the recruitment end to filter resumes and some applicants are using AI to generate a "tailor made" resume to adapt their experience to a given job posting. Its just AI talking to AI and I think this might start to become a common theme in our society.
- deleted 1y ago[deleted]
- higeorge13 1y agoLet’s hope ai hacks mailboxes and google meet, and eventually replace c suite and managers as well. We might get more ‘reasoned’ and deterministic engineering roadmaps or financial strategies by claude ceo/cto/cfo/vp/director agents than current leaderships. lol
- Omerfishel 1y ago[dead]
- tvarghese7 1y agoReminds me of DOGE :)