281–290 of 305 posts
Anyone got a good opensource Jira alternative I can install locally? Most alternatives are cloud as well.
Wow. This must feel like a huge fuck-you to people that migrated to Atlassian because they could host things locally (I worked at a place that made the leap 3 years ago and it was a somewhat controversial decision. I feel kinda bad for everyone that'll be hearing an "I told you so" on Monday morning). Not only is the product being killed, they're raising the price during the migration period. Their FAQ also hints tha…
It's the Oracle playbook. F*ck customers, make money. Seems to work rather well, actually!
Are there good self-hosted alternatives for those of use who'd like to get off of Atlassian products? For Bamboo, I immediately think of Jenkins, although it's showing its age now. For Confluence, I think of Media Wiki. For BitBucket, I think of self-hosted GitLab. Not sure about Jira or Service Desk, though. I'd appreciate any better suggestions.
Disclaimer, I am CEO
Earlier quoted context omitted.
Our org uses both Jira Server & Confluence Server - and I’m fairly sure this will make us move away from Atlassian’s products The split between cloud and server offerings is partly to blame here My thoughts go out to the businesses that have built plugins for Jira and had to endure the variances between cloud and server, or worse, only catered for the server market. The group at tempo timesheets[1] particularly come…
Yes, there still is no easy way to migrate Tempo data from Server to Cloud. Their advice is "there's an API - good luck" [1]. Gitlab is great for their developer niche, but the relatively weak issue tracker and wiki lets them down for more general use. Still, Gitlab is a great company with momentum and a roadmap. Feel free to join us [2] in looking at such alternatives. [1] https://tempo-io.atlassian.net/wiki/spaces/…
"Relatively weak issue tracker and wiki" got me interested - mind elaborating in more detail what brings you to this conclusion? :)
Thanks!
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 smaller instances running around that basically have nowhere to go now. There are several industries that are incline to stay on premise: healthcare, legal, and financial software among others. We’re in that same boat.
At the moment, I’m inclined to recommend we drop Atlassian altogether, for several reasons:
First, Atlassian has never really understood the needs of large enterprises. They’ve recognized that we need performance and scalability and top level web security, but the rest of our large enterprise requiements remain largely unmet.
Secondly, I haven’t seen any good organic development from Atlassian for a long time. They’ve bought a lot of other products and companies, but their ability to produce and deliver great features disappeared a long time ago.
Finally, I have no confidence that Atlassian will keep the data center products going and properly maintain them. Something tells me they’ll do what’s necessary to keep too many customers from immediately jumping ship, but in the long run, I expect we’ll eventually see the end of life for the data center products just like they’ve done with the server products.
Earlier quoted context omitted.
Yes, there still is no easy way to migrate Tempo data from Server to Cloud. Their advice is "there's an API - good luck" [1]. Gitlab is great for their developer niche, but the relatively weak issue tracker and wiki lets them down for more general use. Still, Gitlab is a great company with momentum and a roadmap. Feel free to join us [2] in looking at such alternatives. [1] https://tempo-io.atlassian.net/wiki/spaces/…
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!
You really don't know why Gitlab is not an issue tracker like Jira is? I'm sure you do, or at least you should know. Being an issue tracker like Jira is not even a bad thing! So why try to look like you think you can be as bad as Jira?
/rant (from a Gitlab fan)
Earlier quoted context omitted.
I agree. this is a jump-the-shark move. I've worked with confluence and jira and they are not as good as other products - but we can put any kind of confidential data in them. Everybody likes sharepoint/google docs/slack way better.
I feel like SharePoint and Google Docs are fundamentally different products that Confluence. Looking for a Confluence competitor with permissions, version tracking, templates, and search but don't feel like I have found a good alternative.
Earlier quoted context omitted.
> I’m hoping that an org like GitLab is able to keep building on and catering for this space. That's not really an option for organizations whose main product isn't code, no?
We (GitLab) have strong planning features but are missing workflow enforcement. GitLab also has a wiki but it is less user friendly than Confluence.
Are there good self-hosted alternatives for those of use who'd like to get off of Atlassian products? For Bamboo, I immediately think of Jenkins, although it's showing its age now. For Confluence, I think of Media Wiki. For BitBucket, I think of self-hosted GitLab. Not sure about Jira or Service Desk, though. I'd appreciate any better suggestions.
> For Confluence, I think of Media Wiki. Having used and looked inside both Media Wiki and its enterprise fork BlueSpice, I can't really recommend either if you need anything more serious than just "minimum viable wiki features". A few years back we temporarily switched from using Confluence to Xwiki, which worked okay for a while, but then different small and medium issues kept adding up until we had to go back to C…