4 ms·
>JIRA sucks. i used to think the same until i had to use azure devops. i legitimately miss JIRA nowadays.
by fernandotakai 2y ago
>JIRA sucks.
i used to think the same until i had to use azure devops.
i legitimately miss JIRA nowadays.
- TheRealPomax 2y agoJIRA sucks, and amazingly there are products out there that suck _even more_.
- badgersnake 2y agoJust because you found something worse it doesn't mean the first thing doesn't suck. CVS isn't good because Visual Source Safe exists.
- makeitdouble 2y agoOne issue is that many many ticket management solutions suck a lot more that JIRA. As an analogy, it feels the same as saying "git sucks", and going on a journey to try CVS, SVN, VSS, DropBox's version management, Apple's TimeMachine, Synology's file management etc. to discover the strength and weakness of these random solutions one by one. At the end of the day you end up really liking git, but when telling to people that git is really great you're met with grunts and middle fingers.
- nickpeterson 2y agoMaybe you end up using fossil?
- marcosdumay 2y agoFossil sucks in its own specific ways, that are different from git's, but still exist. And that's the issue most people on this thread miss. If every tool for reaching some goal suck in some way, do the best of them really suck?
- deleted 2y ago[deleted]
- fernandotakai 2y agoi mean, i never said jira was good. i said that it was not as bad as azdo. after 17 years working as a dev, i came to the conclusion there's no good ticketing system, there's only less-bad-ones. and i honestly think a well configured jira instance is the pile-o'-shit king.
- m_rpn 2y agoADO is not worse than JIRA... it's just a different kind of worse.
- ike2792 2y agoI used to think JIRA sucked until my company migrated to ClickUp. In general most of the tools can be made to be usable if a tech lead or engineering manager can tweak them to what a team actually needs. Usually they are left in the hands of TPMs or Scrum Masters who generally make the whole process too heavyweight and complicated.
- jraines 2y agoYes, ClickUp was the worst I’ve used out of Pivotal Tracker, Trello, Wrike, Jira, Excel, Notion Calvinball, threatening emails, or text files
- EGreg 2y agoWhat would y’all say are their best features? The must haves done right? Our team used Redmine from a decade ago, but people like all the pretty ways to drag items between columns or something
- fernandotakai 2y agooh wow, redmine! i worked at a place back in 2008 and we used redmine -- i even wrote a plugin to track worked hours so we could properly bill clients (i ended up learning rails because of this).
- Izkata 2y ago> Notion Calvinball You got me looking, but this doesn't seem to exist. I kinda want to see a Calvinball issue tracker now.
- Izkata 2y ago> Usually they are left in the hands of TPMs or Scrum Masters who generally make the whole process too heavyweight and complicated. This is what happened to us for years, trying to create a common process for multiple teams on the same jira project. Then the manager that oversaw those teams left and during the last reorganization we all split up into our own jira projects where each team could configure it however they wanted. There's still rough edges, like with how links are inconsistent, but overall it's been pretty great since then.
- stemlord 2y agoSame, now that I'm forced to use Monday. Jira was so feature rich and power-user-friendly in comparison.
- JohnFen 2y agoHaving been inflicted with both, I agree that if I have to choose between the two, Jira is the lesser evil. Azure devops makes almost anything else look great by comparison.
- TeeMassive 2y agoI just want an issue tracker with a customizable sate machine to transition status.
- tempodox 2y agoI suggest there could be some confusion at play here: It's not so much JIRA that sucks, but the processes being implemented with it.