Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Is JIRA better or worse than Azure DevOps?
We're being moved over to JIRA and I'm worried because I hear so much shit about Atlassian
One of the big problems with JIRA is it's extremely configurable, so your experience depends entirely on how your admins have set it up. If your company is the type to micromanage, JIRA gives them a lot of tools to do that, which I think is why it gets so much hate from devs. I find it tolerable in my current job but it's definitely designed for managers and not for developers.
Jira gets double whammy:
This is basically every major enterprise ticketing system. They're typically extremely customizable over-featured behemoths so that they can check all the buzzword boxes for the people that make purchasing decisions but will never actually use the system.
"It's a fully integrated Agile ITIL DevOps CMDB that empowers your users while providing generative KPIs to guide business decisions!”
Then, on top of that, ownership of it is generally dropped on a team that is completely incapable of properly managing it from both a technical ability and sheer manpower availability standpoint. So each install ends up becoming an overly complex, confusing, terribly performing mess.
I think I've seen one reasonably well managed install in the couple decades I've been doing this, a couple of more that were mildly jank but usable, and then everything else has been a pit of despair largely driven by the above.
Honestly I never had a problem with JIRA.
Over all the project management tools I've used in my decade of work, Atlassian's suite was the most organized for my needs.
The most annoying part is reporting, which I hear a lot of complaints about. But that's not my job, and the reports I need are easy to export the data and build a custom UI to organize it.
We actually moved from JIRA to Azure DevOps. Part of it was that Atlassian dropped the server version of JIRA and we weren't too keen on moving to the crappier cloud version.
I'd say it's different. Some things JIRA does better, some things Azure DevOps does better. You eliminate some pain points, and end up with some new ones.