Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jira Is Turing-Complete

seriot.ch

Post reply on HN
Print view View original

101–110 of 160 posts

Re: Jira Is Turing-Complete

#101

Post by FridgeSeal »

Cockbrand wrote: post #59
taspeotis wrote: post #20

I came back to a workplace, that still used JIRA. Obviously during the interview I was like oh JIRA yeah yeah yeah you still use that? I can use that. Anyway yes, I can use JIRA. But it was a real shock to see the latest version of JIRA. It has a thousand papercuts, one of the worst is double clicking on text select stuff suddenly kicks fields into editor mode. What I was remembering was JIRA Server 4.0, you can walk…

My day job doesn't require using Jira or similar tools any more, so from a perspective of genuine curiosity: what's the consensus among entire project teams (not just the nerds) for a better alternative?

Linear.

By far and away, linear.

The task tracking features you actually use, it’s fast, you don’t waste a billion years playing “who knows how to do this and has the permissions hell” that you would with Jira. The integrations work properly. The layout and UX makes sense, and all the nontechnical people I’ve used it with liked it and had no issues with it.

Re: Jira Is Turing-Complete

#102

Post by [deleted] »

jiggawatts wrote: post #30
Groxx wrote: post #16

Earlier quoted context omitted.

Quite a few have, the issue is that every Jira instance is a fractal shit snowflake of custom properties several layers deep through old failed migrations to new organization strategies. And many times the API can do stuff that the UI doesn't allow, and everyone's relying on the UI to drive things, so you end up in weirdly broken corners because you didn't notice that you need custom_field_5537 to be paired with cust…

I just had a thought: is there some API so obscenely baroque and painful to use that even AIs would flatly refuse to work with them? It would be an interesting exercise to keep feeding a coding agent ever crazier interface designs until it cracks. “The base64 of the rot13 encrypted EBCDIC string has to be included in a JSON in the XML SOAP request, but both the JSON and XML escaping is manual and incorrect...” "...bu…

[deleted]

Re: Jira Is Turing-Complete

#103

Post by mavamaarten »

unconscionable wrote: post #24

Woof. JIRA is so slow, and managers never seemed to set it up correctly. I have trauma from using it!

Yeah the slowness is what always gets me. Like in essence a ticketing system isn't more than just a database of tickets and relations between tickets and states. And okay you can kinda make it explode by having tons of interconnected tickets and custom fields and plugins. But I will never understand how something that just works with simple textual data and attachments can be so unbearably slow.

Re: Jira Is Turing-Complete

#104

Post by ivan_gammel »

vjvjvjvjghv wrote: post #95
ivan_gammel wrote: post #81

Earlier quoted context omitted.

A dysfunctional organization will project its failures to everything it touches. I personally have not seen such mess, likely because working in regulated industries means there‘s usually some SOP or work instruction that is regularly updated, so the setup is driven by the compliance process. Nowadays, I opt in for Atlassian because it works fine out of the box, I avoid heavy customization (which would mean tool lock…

“ I personally have not seen such mess, likely because working in regulated industries means there‘s usually some SOP or work instruction that is regularly updated, so the setup is driven by the compliance process” I work in medical devices and our Jira is a mess too. Seems a lot of people try to solve process problems by customizing Jira.

„Every organization thinks that they are unique, yet they all are doing the same thing“ (a quote I heard last time from an SAP consultant, which is probably a common knowledge or some named law).

This is the funniest thing about customization of enterprise products. They spent hundreds of years on user research and product development, so chances are high that their standard solution is sufficient for your problem, and you don‘t need anything else. Yet too many people are tripping on the hard problem of enterprise products: the custom fields, which they hardly even need.

Re: Jira Is Turing-Complete

#105

Post by malfist »

chuckadams wrote: post #99
crabbone wrote: post #73

Earlier quoted context omitted.

I can see very naive points here: * "Corporate hackers" is a... not a very common thing. In the corporate world most programmers do what they are told to do and nothing more. Initiative is punishable. * API wrappers aren't actually good. Not to mention that the API itself is very poor. JIRA has a tradition of arbitrary changing things, especially removing things, or not exposing the useful functionality. It's not a w…

I've worked for a few Fortune 50 companies, and they all had "shadow IT" that would crank out scripts and tools with no official sanction to work around the cumbersomeness of the official tools (or sometimes their complete lack). That's what corporate hackers are.

My other half is one of those. Works in setting up hospital pharmacies for new hospitals and he's the "excel and VBA guy" to all his coworkers.

It's amazing how far just a little bit of programming can

Re: Jira Is Turing-Complete

#109

Post by lq9AJ8yrfs »

jiggawatts wrote: post #30
Groxx wrote: post #16

Earlier quoted context omitted.

Quite a few have, the issue is that every Jira instance is a fractal shit snowflake of custom properties several layers deep through old failed migrations to new organization strategies. And many times the API can do stuff that the UI doesn't allow, and everyone's relying on the UI to drive things, so you end up in weirdly broken corners because you didn't notice that you need custom_field_5537 to be paired with cust…

I just had a thought: is there some API so obscenely baroque and painful to use that even AIs would flatly refuse to work with them? It would be an interesting exercise to keep feeding a coding agent ever crazier interface designs until it cracks. “The base64 of the rot13 encrypted EBCDIC string has to be included in a JSON in the XML SOAP request, but both the JSON and XML escaping is manual and incorrect...” "...bu…

that's nearly a requirement for anti-bot things. turnstile etc.

Re: Jira Is Turing-Complete

#110

Post by danielcasper »

zombot wrote: post #66
lmm wrote: post #9

That explains why it's impossible to tell whether any given Jira operation is going to halt or not.

Does that count as "you can play Doom on Jira"? Does Jira supply the pump action shotgun required to kill the resulting demons?

I'll need you to submit a ticket to fire the shotgun.
Post reply on HN