by julian_digital on 10/9/22, 9:16 AM with 82 comments
by gw99 on 10/9/22, 10:23 AM
by lbriner on 10/9/22, 10:38 AM
When you have the size and money of Atlassian, that excuse is pathetic. Yeah we have 3000 Developers (or whatever) and we don't have the resources to do good UI design, refactoring away from poor performance etc. I always thought that these companies were the ones who invented "how to do good web apps", but it seems like function over everything and even the functionality is poorly implemented in some cases.
How can anyone think that a simple app that downloads 24MB over 900 connections is OK. What the heck?
by hestefisk on 10/9/22, 10:32 AM
by simonswords82 on 10/9/22, 10:35 AM
Since they acquired Trello I’ve watched them slowly but surely overcomplicate the interface making the product less intuitive.
by _rm on 10/9/22, 10:55 AM
It's such a fantastic lesson: it's a glorified to-do list. They got rich off a to-do list app.
Focusing on the simple things that everyone needs, rather than the complex esoteric problems that engineers enjoy, is where it's at.
by fortnum on 10/9/22, 10:45 AM
by SideburnsOfDoom on 10/9/22, 11:01 AM
The issue isn't Jira; it's the question: Does Jira work for you, or do you work for Jira?
by perrygeo on 10/9/22, 12:49 PM
Jira provides endless ways to engage in useless meta-work, it's nearly the entire purpose of the UI. Style over substance is the result. It feels intentional on Jira's part to woo their target audience - mediocre managers who struggle to produce well-written and well-designed technical content. Dress any plan up with enough fluff and it looks impressive.
by voidr on 10/9/22, 12:37 PM
You kinda need to impose process for large projects, and know where you are. The engineers are free to show a better tool for the job.
> I think Jira does a good job of making teams look much busier than they are, but in the end I see it more as a “talk more not do more” situation.
It does not make teams looks busier, it shows that teams are a lot busier in reality, which is valuable information.
> The Alternative
> Although a potential downside to Linear is that it is built explicitly for engineers, thus may not be suitable for other teams such as marketing, design, etc.
And this is why engineers will never build any viable alternative to Jira, because there is this us vs. them mentality. Issue management tools need to work for the whole organisation, that's why Jira is still the gold standard.
> If you’ve given Linear a try, but it just doesn’t work for you, some viable alternatives include GitHub Issues, Asana, ClickUp, YouTrack, Trello, Pivotal Tracker, and monday.com.
None of these are viable in larger organisations, they are fine for small projects, but you would have a lot of trouble with them in an enterprise context.
Jira's web UI can be very annoying, however an alternative to Jira would need to be at least as customisable and familiar as Jira, otherwise no large team will ever adopt it.
by manuel_w on 10/9/22, 11:41 AM
We're currently looking into outphasing Jira and going to GitLab, but as I see, you can't nest tickets there. Can you? This is absolutely crucial to me. I'm happy for recommendations that allow ticket nesting (Epic, Issue, Subissue) and interface nicely with GitLab.
Thanks!
by bamboozled on 10/9/22, 10:31 AM
* Waiting for it to load.
* Trying to find issues, mostly due to the crap, unintuitive UI and the slowness of said UI.
by turtleyacht on 10/9/22, 7:33 PM
- You can now trigger Status to Done
after merging Github pull request.
- If someone assigns you a story as
reviewer, you can trigger the Status to
In Progress (if not already).
- You can have a story automatically
reassign to the reporter once it's
marked Done.
It would be nice if we could do requirements tracing from business all the way to ITSM change request, track associated defects--some combination of semantic analysis and code grepping--and ultimately dashboard all this.
It seems like it would approach the model of a thinking organism.
by kisamoto on 10/9/22, 11:02 AM
Huge machines capable of doing everything.
As a result, unable to do anything particularly well.
Bloated, expensive and only still in business because decision makers know the names and the vendor lock-in is huge.
by scombridae on 10/9/22, 12:23 PM
by pacifika on 10/9/22, 10:25 AM
by grashalm on 10/9/22, 10:57 AM
by m0zzie on 10/9/22, 10:59 AM
Don't get me wrong, I can be as frustrated by Jira as the next person, but this is simply a rant fuelled by the writer's anger at internal processes as much as the software itself.
Additionally, the numbers on data usage and network requests do not align with what I see.
It's just a couple of fair points surrounded by populist "yucky Jira" fluff.
by y42 on 10/9/22, 2:56 PM
Yes, Jira can be pain in the ass. Because you are not able to adapt your workflow. Jira offers a thoughtful solution to manage your progress and processes.
The problen sits infront of the display.
by pentagrama on 10/9/22, 4:12 PM
Also other thing from this articles "I hate [tool]" is that many people just don't like their job or are burned out, the hate may be coming also from that, not only for a poorly designed tool.
by eurasiantiger on 10/9/22, 1:28 PM
by iso1631 on 10/9/22, 2:13 PM
by strictfp on 10/9/22, 10:25 AM
A simple list is a pretty good solution IMO.
by Tknl on 10/9/22, 10:25 AM
by strictfp on 10/9/22, 10:24 AM
by Overtonwindow on 10/9/22, 11:43 AM
by bhaak on 10/9/22, 10:35 AM
Apparently you can only get "loads fast" or "is usable" and not both. But when in doubt, I'll choose usable.
by polotics on 10/9/22, 11:40 AM
by 9wzYQbTYsAIc on 10/9/22, 10:55 AM
by iamgopal on 10/9/22, 10:25 AM
by Comevius on 10/9/22, 10:23 AM
by arrakeen on 10/10/22, 3:39 AM
by jkmcf on 10/11/22, 2:28 PM