>JIRA sucks.
i used to think the same until i had to use azure devops.
i legitimately miss JIRA nowadays.
i used to think the same until i had to use azure devops.
i legitimately miss JIRA nowadays.
CVS isn't good because Visual Source Safe exists.
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.
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?
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.
Our team used Redmine from a decade ago, but people like all the pretty ways to drag items between columns or something
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).
You got me looking, but this doesn't seem to exist. I kinda want to see a Calvinball issue tracker now.
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.