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

61–70 of 160 posts

Re: Jira Is Turing-Complete

#61

Post by zelphirkalt »

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…

About the double click into edit mode: Yes!! So much this! So annoying. Even basic text stuff they get wrong! But you know what a project manager told me ... They _like_ that, because they never use double click drag to select whole words ... ugh. Like always more proficient computer users are dragged down by the convenience for people barely able to use a computer.

Re: Jira Is Turing-Complete

#63

Post by karel-3d »

Groxx wrote: post #16
Buttons840 wrote: post #13

Jira is popular and has good API wrappers for your favorite language. I'm surprised corporate programmers with the hacker spirit haven't automated most of the things they are asked to do in Jira with Python command line scripts or whatever. If you can make Jira an order of magnitude easier to use for yourself than for the people pushing it, suddenly the script flips and Jira is something you push to protect yourself.…

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 am not using JIRA anymore but I guess in 2026 you could write AI wrapper around clicking on UI elements?

Re: Jira Is Turing-Complete

#64

Post by zelphirkalt »

IshKebab wrote: post #44
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…

That version of JIRA could still easily be configured to be awful. That's the main problem with JIRA - the power to actually configure it to be sane is always reserved by a few people who don't want to bother, don't have time and don't care because they aren't really using it every day. Well one of the problems anyway. It's also unimaginably slow, and has weird limitations like issues can't be parents of other issues…

The non-existence or non-availability of recursive features, like an issue being parent of an issue, or in Slack a thread being started inside a thread and so on, to me usually indicates, that the developers of the tool are afraid of recursion, and have never learned how to implement this easily in a database, used a programming language that easily deals with recursion, and don't know how to deal with it in other languages. They tend to think "it's too complicated". It's usually just a silly lazy excuse, but here we are, with tons of inflexible shitty tools.

Re: Jira Is Turing-Complete

#65

Post by Topfi »

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…

> Obviously during the interview I was like oh JIRA yeah yeah yeah you still use that? I can use that.

Hold up, did I miss something? Fall into a time hole? Why are we talking about Jira like it’s Visicalc? Not currently working for an IT company, so maybe I missed something cataclysmic in the past two years…

Re: Jira Is Turing-Complete

#66

Post by zombot »

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?

Re: Jira Is Turing-Complete

#67

Post by halapro »

hyperhello wrote: post #3

Jira is completely awful and thus has the potential to take on any other form of awfulness.

The worst part is that every company with a tasks product works right towards Jira. Compare what GitHub issues were in 2014 to what they are today: https://github.com/features/issues

and they keep. adding. redundant. features

Re: Jira Is Turing-Complete

#68

Post by tailsdog »

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

Re: Jira Is Turing-Complete

#70

Post by baq »

halapro wrote: post #67
hyperhello wrote: post #3

Jira is completely awful and thus has the potential to take on any other form of awfulness.

The worst part is that every company with a tasks product works right towards Jira. Compare what GitHub issues were in 2014 to what they are today: https://github.com/features/issues and they keep. adding. redundant. features

The engineer is not the target user
Post reply on HN