291–300 of 305 posts
Jira is really a weird product; I'm using it for ages now and i have not seen any real features being added in the last 10 years and fundamental issues have not been adressed. The weirdest thing was their UI change a few years back where they thought it would be great to make core workflows 1 or 2 clicks further away than before. Like 'creating a ticket; went behind this plus button thing. Plenty of features i would…
I work for a large company that spends almost $1M/year with Atlassian and I’m the lead architect for our Dev tools infrastructure. On the one hand, I’m glad Atlassian has finally come clean on what’s obviously been their strategy for some time. On the other hand, it kinda sucks for customers like us. Yes, we’re a big company and yes, we run data center instances of some of the tools. But we’ve also got tons of smalle…
What are some the unmet requirements?
Thank goodness! The unicorn I work for will finally ditch JIRA and move on to something more user-friendly. What a relief.
I can't imagine our management will be happy about this. We have server licenses and I don't think we'll be willing to turn our data over to their servers. On the other hand, this is great for me because I pretty much hate using all of these products. If this gets my company to stop using them, I will be so happy.
What specifically sucks about Jira and Confluence?
Earlier quoted context omitted.
Hi, Developer Evangelist at GitLab here. "Relatively weak issue tracker and wiki" got me interested - mind elaborating in more detail what brings you to this conclusion? :) Thanks!
Please stop doing this. Fishing for product insight on such broad opinions in an open forum does a disservice for Gitlab the product and the team. If it was a natural question... But this is so canned, every gitlab employee here does it, sounds flaky and impersonal. Almost troll-like, maybe even arrogant tbh. You really don't know why Gitlab is not an issue tracker like Jira is? I'm sure you do, or at least you shoul…
sorry that it came around this way. I was really interested in your honest opinion, as my personal experience with Jira is limited at this point with 7 months into my new role. I have been asked about it during past GitLab trainings in my old job, but never used it in production myself. May sound weird, but I learn the most from users sharing their experiences :) Hence my question, it would help my research.
Earlier quoted context omitted.
We (GitLab) have strong planning features but are missing workflow enforcement. GitLab also has a wiki but it is less user friendly than Confluence.
What we mainly need is cheap/free non-coding users. I'm really not comfortable paying for a gitlab seat per support staff we hire.
I work for a large company that spends almost $1M/year with Atlassian and I’m the lead architect for our Dev tools infrastructure. On the one hand, I’m glad Atlassian has finally come clean on what’s obviously been their strategy for some time. On the other hand, it kinda sucks for customers like us. Yes, we’re a big company and yes, we run data center instances of some of the tools. But we’ve also got tons of smalle…
"...but the rest of our large enterprise requiements remain largely unmet." What are some the unmet requirements?
Also: email handling sucks and support for the scaled agile model is pretty non-existent.
Just in general though, take a look at jira.atlassian.com and see all the issues with thousands of votes that have been unresolved for years and years.
My employer (large Fortune 500) recently "soft banned" Confluence and Jira, meaning groups already utilizing it can stay on it until our enterprise license runs out at the end of the yearly support contract. At first I thought it was really stupid decision as Confluence, at least, is fantastic product and Sharepoint/Notes (the enterprise replacement solution) is a horrid alternative. One of the admins said there were…
How did Confluence and Sharepoint compare? I'm curious (For context: I've only ever worked in BigCo's that used Confluence).
Sharepoint is god awful for anything Confluence is good at - namely being a wiki aimed at technical documentation. OneNote is a little better but even the online OneNote isn't great great, and both are a few steps backward in functionality.
Earlier quoted context omitted.
My understanding of Jira is that it by itself does not suck but it bends over backwards for asinine “business processes” so it is difficult to find an implementation in the wild that does not suck.
I know a little about the inside of the jira sausage factory from second hand reports. It's got the "accrete everyone else's business processes" problem that you mentioned, but it's also got the problem that it's quite spaghetti on the inside as well, probably for the usual reason - startup founders writing lots of code in a hurry and conflating the purpose of the software with its architecture due to being too close…