People who like Jira (or rather want; I doubt one ever “needs” this thing), and make decisions on its implementation and payment, and force it on others, are not the people who are shopping for alternatives. So who these alternatives are really for?
People who like Jira (or rather want; I doubt one ever “needs” this thing), and make decisions on its implementation and payment, and force it on others, are not the people who are shopping for alternatives. So who these alternatives are really for?
People in companies above 2-3 people have to use _some_ ticketing / task system.
I like Jira. Much more than Service Now
i always quite liked the flexibility of jira and the ability to logically connect tickets etc. I can see how it's perceived as this clumsy corporate tool, but i often whish gh issues had more of the features jira has.
This always irritates me, because it used to be just like that. First time we bought Jira, it was like a (small ) one-off charge on someone’s card, and included full source code to let you build it yourself.
I’m co-developing lots of projects with AI. Right now I have a hand-rolled backlog system that lives in each project’s git repo with a standard prompt on how to create, triage, and review backlog items.
This looks great for me. Better than what I have, smaller/cheaper/more AI focused than Jira.
There's an entirely new class of people doing development with AI.
Presumably some of them?
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?"
Oh, what thing that would be? :)
[flagged]