Sadly, I think Atlassian did the math from a purely economical standpoint, and a community standpoint, and determined that they can afford to lose what they will lose with this announcement.
If I were to wager a guess, the math goes something like this.
Economically, they see the money to be gained by forcing customers to either data center or cloud. They will get 1 in 10 of us server customers to move over to cloud or data center, and that's all they need to break even.
From a community standpoint, they probably have gained enough product champions for their cloud and data center products, that the losses they will experience in community members contributing to their products will not be enough to kill the community support and mod ecosystem around their product.
Unfortunately, the math makes sense from a business perspective. It's very hard to argue with if you are a publicly traded company.
Still super awful to treat their longest standing customers this way.
The economical math is simple. If I look at our app sales, they might not be representive, but the principle should be the same: over 70% of sold licenses are for user tiers below 500, but over 70% of the revenue is for user tiers 500 and up. If I draw the line at user tier 250 because I expect customers to accept an upgrade to user tier 500, it's even 85% of the revenue.
However, for us, it's a matter of attitude not to neglect smaller customers.
You keep asking what we would like to see from Atlassian. I think the key item would be a lower price point for the on-prem product. Even if you raise the prices somewhat compared to server, keep the same tiered structures, 10-20-50-100-250-500.
That would give the lower price points that the smaller customers need to continue to use the product and would provide an entry level cost that would be required to attract new customers and would give us reason to believe that atlassian still cares about on-prem.
Failing that, I would rather hear them say that they are sunsetting on-prem completely in 3 years, rather then this unspecified period of time for datacenter. I'd rather just know for sure that I have to get off the atlassian product vs having this "option" that really isn't an option for most people. You want to be a cloud only company, then say you are going to be cloud only, and be done with it. Let us grieve the loss of a good product (as we have done for many other companies and technologies that have gone under) And start to move on.
This forced transition to datacenter hurts more. Its saying "We like you if you are rich, but otherwise we don't care" Its insulting to the long time community of non-enterprise on-prem customers.
And even then it leave the rich people wondering when they will be cut off. We all know its coming.
@Andrew Laden Great suggestion! I keep asking what people want to see, because this thread has been alot of just poo poo on Atlassian lately. Although one could argue its deserved, I'd like Atlassian to understand what it is we want to see from them, rather than just "Boo Atlassian!"
what are you, like an advocate for Atlassian? :)
[Personal attack removed]
@gzgenm ok, then they just wont get feedback other than "We don't like it." and won't change anything, because no one is expressing what it is they want.
I'm an advocate for getting us, the community, a solution that isn't just spend 10x or migrate to another product. It's cheaper for all of us in the long run if we can get reasonable pricing from Atlassian.
But turning on each other because I'm looking for constructive criticism doesn't get us anywhere. That's why I am encouraging people to post their suggested solution. If Atlassian won't ask the question, I will.
as I said already, they got all the feedback here and told us they're not going to change nothing.
@gzgenm I share your pessimism in one regard. With the lack of responses from the Atlassian Team, it seems little will be done.
However, here's a bit of optimism for you. That doesn't mean they are not reading these posts. The lack of response COULD mean that they have no good answers, and therefor have to go back to the drawing board and come up with better solutions for us. Those solutions may be super easy and obvious in your and my eyes. But big companies like this take a lot of time to change plans they already made and are already executing.
Admitting defeat is not a profitable move for a publicly traded company. So, rather than do that, they are HOPEFULLY tweaking their plans, based on our massive amount of feedback.
All I can recommend is that you continue to provide more information about how this decision doesn't work for your organization. You've mentioned that price is a factor. I agree, that's been beaten to death on this forum.
But what other factors are preventing your move to the cloud? This is not me advocating the cloud, so much as me trying to continue to prove that Atlassian is wrong, and needs to change their plan. The cloud is not for everyone, and it feels like they really need to get that through their heads. Trust me, this organization will not be moving to the cloud any time soon.
The more specific issues with their plan we can bring up, the more we can influence its future.
@Alex Janes , you must be kidding me.
Open hecking docs and take a look yourself
https://support.atlassian.com/jira-cloud-administration/docs/what-are-the-differences-between-jira-cloud-and-jira-server/
no external user managment
no ldap/ad user management
no jelly scripts
no custom workflow
no company corporate domain
and just for u to laugh on: our instance has 5TB data.
250GB? LOL.
It is what? The future? Without even support of corporate user management?
You have to pay not only to cloud, but to premium version of it plus "atlassian access" which has NO direct support for either LDAP nor AD.
They cease Bamboo server the same date they stop selling Jira! and they have ABSO-hecking-LUTELY nothing to offer as a replacement.
Don't mock me please, it's the worst possible decision they made.
THE WORST. They put money before reason. They are not ready to make such an important step yet, they don't have a class product to sell, but they're selling it anyway. Selling it with triple the old price, which I should tell you wasn't small at all.
I'm not investing a second of my time no more.
@gzgenm I am not mocking you. In fact, I am on your side. I have a lot of concerns about the differences between cloud and server. That is why I am not moving to the cloud.
I'm asking you to provide specific examples of how each of those items affects. If we just say "it's different, therefor its bad" Atlassian will tell us to pound salt and will not help us.
Could you go into more detail as to how each of those items affects your organization?
For what reason? You know, it takes a lot of time explaining every other thing. What I get in return? declaration that "cloud is the future"? or that I should pay triple price and have less because Atlassian wants me to?
| Attachments | 1057286 |
| Comments | 4030833 |
| Components | 2566 |
| Custom Fields | 131 |
| Groups | 1898 |
| Issue Security Levels | 9 |
| Issue Types | 43 |
| Issues | 874656 |
| Projects | 193 |
| Resolutions | 10 |
| Screen Schemes | 27 |
| Screens | 124 |
| Statuses | 87 |
| Users | 46569 |
| Versions | 3669 |
| Workflows | 23 |
is it enough?
We rely almost on every thing server instance can do. And cloud can not.
You know, it takes a lot of time explaining every other thing.
@gzgenm I understand. But not explaining it leaves Atlassian with all of the power. If we don't explain it to them, then they can come right back and say, "Well you never told us why..."
A lot of people here, including myself, have spent a lot of time explaining in great detail why this decision is bad for us. You are not alone in that regard.
Everyone here (save for Atlassian Team) seems to share your view that this is a bad decision.
We rely almost on every thing server instance can do. And cloud can not.
Can you give specific examples of some things that these limitations prevent you from accomplishing? Unfortunately, Atlassian's response to the numbers you gave about how big your server instances are, would just be "We have enterprise edition for the cloud that can handle your needs." I 100% agree that is a terrible response from them, as it simply ignores the fact that you don't want cloud.
But if we can't succinctly explain our issues in detail, then Atlassian will just keep coming back with the same talking points.
I only keep responding, asking for more, because I've gone through this song and dance for the past few weeks with Atlassian, and I know how they are going to respond to the points you are making. I want them to see why it doesn't work for us. And I am trying to get you to explain it to them.
I am on your side. Please understand that. I am only trying to get you a response from Atlassian that isn't more talking points. But if we as users can't give anything more than, "Because Cloud is missing those features." Yes. But what does that prevent you from doing?
Perhaps I'm not being clear. So allow me to provide an example.
You mention "no custom workflow". Ok, but how are you using custom workflows that blocks you? For my organization, this point is a deal breaker. The authorization workflow for approving medical procedures has very specific steps configured to make sure that we are following compliance with regulatory requirements. Without custom workflows, I cannot ensure that compliance.
How are you using the features you mention are missing in cloud, and how impactful would it be to your organization? These are the types of things that Atlassian needs to know.
EDIT: I guess I'm missing something. But it looks like custom workflows are available in the cloud. AGAIN, not going cloud. But that specifically does not appear to be a truly missing feature, unless you are counting low code type modifications to Jira itself.
@gzgenm I understand this is a frustrating topic and emotions are running high, but keep in mind that attacking other users or Atlassians personally is against the rules here and may result in your account being suspended or banned.
I've edited out some comments about both @Alex Janes and the Atlassian team, and would ask that you please review our Rules of Engagement before continuing to participate in this conversation.
Thank you!
@Monique vdB Although I do appreciate you taking action here, I would like to point out one thing. Please feel free to remove this quote if you feel my posting it again violates the Rules of Engagement.
They don't need you. Neither do we
Although this statement is rude, and a little harsh, I think it's safe to say that it succinctly summarizes how everyone feels right now. It feels like Atlassian has said this to us through their non-responses, and empty talking points. We, as a community don't feel engaged with, when the response is to just restate the same talking points, but in a different way.
The problem I am seeing here is...
I am happy to give more feedback on this if you feel it is necessary. But I think it's safe to say that the collective mood of the community posting in this thread, is summed up with the ^ above ^ quote...
@Alex Janes it's possible I misread that quote! I thought "you" in that sentence was referring to you, Alex, and read it as a personal attack. It was also reported to the moderators in that light.
I apologize if I misread it. If it was meant as a more general comment about how users are feeling, it would not go against the rules. It's absolutely fair to raise the concerns about the general community mood and I do appreciate your taking the time to articulate it.
I can tell you from the inside that people at Atlassian truly do care and do empathize, but if it doesn't feel like it from the outside, that's really good for us to know. I'm glad you've signed up for the feedback group, and hope that will be a constructive channel to raise feedback and, importantly, feel your concerns are heard.
Let me know if there's anything else I can do.
@Monique vdB It was a personal attack in the context of the original post. But I didn't react to it, because it's hard to blame him. It's a tense time for Atlassian Champions. And without more communication from the Atlassian Team, I'm afraid this mood will continue.
The quote was just so, apt, that it was very useful in explaining my point.
And similar situation with our company, was trying to spend >$10k on Jira/Conf Server to increase number of users to 50, but I guess these are small amount for Atlassian.
@Monique vdBIMHO this is not mainly an issue of managing emotions. There are several reasons (not just less $$$) that have driven the decisions of many of us to go with server. Starting with air-gapped systems, Privacy Shield legislation, regulated industries, customer requests to things that do not work on your SaaS offering. As they are/ were killer criteria in the selection process, this process has to be redone with all possible offerings...
BTW: It cannot be the task of us/ the community to collect those features for Atlassian marketing. And especially not after the decision is taken (I once learned that you collect facts first, then make decisions, but this was before the post-factual world).
@Monique vdB"I'm glad you've signed up for the feedback group, and hope that will be a constructive channel to raise feedback and, importantly, feel your concerns are heard."
Aehm... This sound a little bit like lying on a sofa of my psychoanalyst... The Atlassian team has now heard at least 4 weeks about our concerns. Is it too much expectation to get feedback on our concerns?
What are you (=Atlassian) actually gonna do with our concerns? Any chance you (Atlassian) is going to revise it's decisions? Or publish a plan to react on our concerns?
And:
When are you (=Atlassian) actually gonna do something?
We won't wait on the sofa for long!
@Thomas Dörfler Cameron did post an update with feedback on the top concerns raised. In case you didn't see it, the post is here.
@Monique vdB: thank you for your direct reply and thank you for pointing me to the post.
Nevertheless I am not convinced cloud is better for us than our private server.
Why?
On private server, we could easily make sure that only company members can access our Jira instance and its data:
- set it on a company owned server
- protect it with proper firewall and safety measures
-> that's it (more or less).
What is on cloud (IMHO):
- Pro: Atlassian will encrypt and protect data and store it in Europe, that's fine (and nothing more than what we do on our server)
- Con: For each App supplier, the data seems to move to a different country.
- Con: The list of suppliers will change over time. Currently there is non in china (but in US). Will this change over time? If Atlassian decides so, it will.
- Con: Each country involved may use its local law to enforce access to our data (am I right on this?)
- Con: Cloud solution is on the move, so I have to monitor and recheck whenever the cloud's legal constellation changes
- Con: I have a time of 45 days to object to legal changes. When I object, I am out. Services are inaccessible for me
So: what is the gain for me and my company? And what is the loss?
I agree, and surely Atlassian have thought of all these pros and cons, Cloud is not the choice for Server users! They have to be able to move Server users to Datacenter at least, even as low as 25 users.
@Monique vdB: one issue I just received today: For a project we are going to receive information under an NDA from our customer. We may want to apply part of that information to our Jira instance. If the information gets disclosed to others, we will be liable for the (unlimited) damage the disclosure creates.
So: if we trust this piece of information to a cloud based Jira instance and, out of some reason it gets disclosed (e.g. through a breach of Atlassian's or Amazon's or an App provider's security measures): Will Atlassian compensate our customer for the financial damage?
Or do we simply have to trust?
Atlassian will say "Sorry" and ask you to pay a new bill
I think many of us just can't afford the new prices anymore.
LOL, Atlassians want to cease bamboo server as well by the date and they even don't have a good alternative to it in the cloud.
You've just **** up your customers in many ways. It's time to remove that promise, you don't value it anymore. You're robbing us and telling us that it's not what we think it is. That's it. It's obvious for 1st graders right after one calculates all the expenses.
I used to be with you for like a decade, since IDK JIRA 3.0 mayb.
I was like an ambassador for your product whenever I could, truly lived with them.
Now it's over. I've seen enough here to understand what you're doing, how you're doing and what you really think about all of us.
Think I'll start a migration process from Atlassian Ecosystem ASAP, that would be an investment - in a year perspective I will be helping the customers you ***** up to move away with as less damage to their workflow process as possible. I believe they will be ready to pay a dime for it.
1. Your cloud isn't ready to replace server
2. Your cloud is more expensive
3. You ***** up, starting with the stupid deadline
Go get your money, now it's the only thing you're looking for.
Hi @gzgenm
Your post was automatically caught in our spam filter, and I just went through and un-moderated it. This FAQ item might help.
Our community has an automated spam filter than sometimes catches "real" posts in addition to spam. All our admins and moderators check the quarantine regularly and will release your post as soon as we can.
Thanks for letting me know this happened, your post should be live now.
Andy
@Andy Heinzer If I were to guess, some of these auto-moderated posts are being filtered because the emotional state and aggressiveness caused by these announcements. That doesn't necessarily excuse all behavior. But it could be why.
Is it possible to update us with why a lot of these posts are getting caught? It seems like there must be a pattern, such as detected profanity or aggressiveness that is catching these posts. I know the FAQ gives some information. But perhaps a little more detail with examples as to what is triggering it may help other users in posting more constructive criticism, and be a little less aggressive in their posts. :)
I think this group is the fake. They have to pretend they are open like someone's opinion could change the way they have chosen.
It won't. You can't expect any constructive criticism from those whom you just ****.
@gzgenm That doesn't mean you can't provide constructive criticism here. What would you like to see from Atlassian? They have already confirmed there is no way server is going to be saved. So what else would you like to see then?
Also, please don't derail me trying to get the auto-moderator issues addressed.
Hi @Alex Janes
Our Community site sees a lot of traffic. This tends to draw in spammers to the site. While profanity can sometimes trigger these automatic spam detections, it is not a guarantee of being marked as spam. In my opinion it tends to happen far more often with new accounts to the site AND/OR accounts that have very few posts. One technique we have seen actual spammers use is to post seemingly benign comments to old threads in order to try to build some reputation or credibility and then go back and edit their original post to include a spam link to some site in order to try to drive traffic to their site or improve SEO (search engine optimization).
In this particular case, the user gzgenm had not posted to Community before this particular thread, and that user edited one of their own posts shortly after creating it (not this post, but the actual post that was marked as spam was edited). In my experience the automatic filter tends to rank these two factors highly likely as spam. Of course it was wrong here, and we have moved this post back out of our spam filter.
I hope that helps to answer your question.
Andy
@Andy Heinzer Thank you for that explanation. That explains why we have seen so many posts being moderated lately when it comes to these threads. I imagine a lot of new users who have never posted before are coming out of the woodwork to express their concern with this change.
1. Atlassian throughout all these years forced us to migrate our accounts from one system to another and back, merging them, splitting etc, so when it could look like a new one, it's not.
2. I express my own opinion using words from Atlassian's famous statement which declares they "don't **** customers" that's why I can't use my work account with links to my company, colleagues and things, sorry about that.
I filled out the form for the "Server Champions" But I don't think they liked what I had to say. So I haven't gotten a response yet. The name "Server Champions" is a bit of marketing misdirection.
A "Server Champion" would be someone who want to champion the cause of keeping the on-prem jira product. All the Server champions are the people on this threat who are explaining why they cant go to cloud or don't want to.
What Atlassian is looking for is not "Server Champions" but "Ex-Server Cloud Champions" People who are or had been on server to to provide feedback on what cloud needs to make it more palatable for existing server champions to want to give up their on-prem installations and migrate to cloud.
Its fine that you want a group for that. Get your customers to do your marketing and all. But don't go and name it "Server Champions" as that is just an insult those of us who have been championing the Atlassian product suite on prem for years and now are feeling completely betrayed.
Can confirm, I also have not heard anything from the Server Champions group.
I also agree, calling it Server Champions is a bit confusing, as server is going away, and we can't champion it anymore. Hopefully it isn't just a group for cloud improvement, and will actually be a group to gather feedback about how to handle the transition to BOTH data center and cloud.
I'll tell you how to handle the transition to DC or cloud:
pay twice more than you paid for server (and pay it every year from now) for DC
pay 3x more than you paid for server, get 3x less than you had (give up all the features and apps and works and integrations and workflows etc etc) and start over from scratch for CLOUD
Apart from this - we're all fine. thank you.
at very least I expected them to set a more reasonable date for the selling deadline.
It's obvious, a community reaction is sooo predictable. And they did it anyway.
I want them to stop bullshiting me about this and that, because we all know that the only reason for them to do it is money. And they don't have a product to justify that (3x+) price. Just don't have it. Okay, you're the boss, just tell us "sorry guys, we don't have any other options and want you to pay upfront for features we maybe delivering in Q4 2021 or 2022 or maybe not" That the honesty I expect from one of the greatest company I've known.
All the solutions had been mentioned here more than once and all the answers were given.
I don't feel there's the need to repeat it again and again giving them more chances to tell you about roadmap, promises and things. They know what they're doing and not going to give a hand to noone.
@gzgenm I recommend filing a support ticket to get a lot of your questions answered, then come back here and post any remaining concerns.
I'm not saying they will have the answers you like. But, unfortunately, that is the best way to get a response from them.
Also, I recommend sending your concerns to the founders. https://www.atlassian.com/company/contact/contact-ceos
Make it heard by the decision makers what your concerns are.
A few ideas have been floated around including the below. While all would be nice to have, for us and our clients items 1 and 2 would be extremely helpful since there is just no time to budget anything even remotely close to the Datacenter costs as they exist today:
Many of us here simply can't migrate to the cloud for a variety of reasons (in our case long term contractual and other) and so it would be nice if Atlassian could help us out so that we may continue operating in the same manner we have been.
Yes, it is understood that the licenses we currently have will continue to function in perpetuity, but some of us are growing and project a need for 25 or 50 user licenses in the third or fourth quarter of 2021. However at present there is simply is no money to buy what's needed now and so we are stuck. Budgets won't be created and moneys allocated until after Feb 2021 and that's the problem.
If Atlassian could at least address items 1 and 2 above then that would be great, but if they are holding out with hopes we will move to the cloud, then it just can't happen unfortunately.
I haven't heard back on the server champion either form either. Not sure what the next steps there would be. But as far as I know we are all still waiting to see what the server champion group will entail.
@David Willson , @Alex Janes , @gzgenm the Server Champion groups are still in progress, we ran into some technical issues in setting them up and need to make sure they work well, so you have a good experience. @Mandy Ross is helping with these and may have some more info so I am mentioning her just in case.
Right on! Thanks :)
@Andrew Laden- got the email today about the groups, your statement is accurate "What Atlassian is looking for is not "Server Champions" but "Ex-Server Cloud Champions.
Looks like DC is getting no love.
One suggestion I have would be to adopt the approach that Azure pipelines takes with subscriptions. Instead of charging customers lots of money the moment they hit 11 users, if the first 10 users were permanently free and not counted in the licensing requirements, then that would make paying for cloud a lot more affordable for smaller businesses. It would also make scaling up a lot easier for smaller businesses.
This, of course, is separate from the other criticisms I've made that prevent us from reasonably going onto the cloud, but it is a suggestion.
And not a bad one at that. Although I am a huge fan of the $10 license fee for 10 users, that first jump to 11 users is a massive increase. If it could instead be only charging more for each individual use beyond 10, rather than, "Oh you are at 11 now? Well, were gonna increase the price for your first 10 users as well." Well, wait a second, suddenly expanding means paying a ton more for my base business, leaving little for the actual expansions of my business.
So, I definitely agree with this suggestion.
Looking again at this discussion thread, it's 4 weeks old now. Many users have expressed their anger, some users have expressed their specific concerns, why they can't migrate to cloud.
Within these four weeks, the only substantial answer (IMHO) from atlassian was "cloud is the future". It's a cool statement from a cool company. But unfortunately, IMHO its cool air and nothing else.
Yes, cloud will bring some improvements, but at the price of too many disadvantages. Many users have mentioned this. Atlassian promised to listen. But obviously Atlassian doesn't care.
I do. And therefore we will check our existing licenses to last long enough to comfortably migrate. Not to Atlassians cloud but to a yet to find alternative that understands our requirements. And not only understands, but also cares.
See you on a different platform!
Atlassian promised to listen.
Yeah, that's why I stopped looking at these threads. Their version of listening is, "Oh, you can't go on the cloud because of compliance reasons? Well then go to our overpriced Data Center offering which gives you nothing more than the on-premises server currently does. You currently have a 10 user license? Perfect, our minimum 500 user license is tailored just for YOU!"
And, "That's on our roadmap (but ignore the thousands of opened tickets on things we've never resolved over the years - we're "sharpening" our focus to do better)."
Or, "You just aren't ready to go on the cloud yet. But here's why you're wrong..."
And my favorite, " ." (As in, we don't have a talking point to answer that question and you don't have enough licenses to make it worth our time to even respond to you)
The exit from the server licenses for Jira / Confluence is a big problem for us. As a company we are too small for the data center and have the target to work WITHOUT the cloud. So we have to think about how we are going to position ourselves in the future.
Hello,
we and our customers are not willing to change to DC for the additional cost.
We and the companys we support have some special in house developed plugins and use some database connected reporting.
Additionally we have highly sensitive data in the system a switch to cloud will never be possble.
So we hope for more favourable pricing with DC in the region of server. Starting with a 10 User licence we use for update Testing.
Else we will have to make plan to migrate to other products.
Cheers
Fabian
My Atlassian spark and excitement has gone out. As a result I've decided to step down from the role of community leader.
People are important, and any one person, statistically might not be. As just a individual I likely will fall into that category. That doesn't invalidate the sadness and disappointment that I feel, but when you stop caring, and when the thoughtful forward thinking messages sent by Atlassian
about building great teams, now ring hollow, instead of creating inspiration, it's time for change.
I am still gobsmacked by the fact that Atlassian is willing to write off 30 000 customers.
"It will be difficult to forecast how our 30,000 server customers will react to our recently announced end-of-life plans" (page 15)
https://s2.q4cdn.com/141359120/files/doc_financials/2021/q1/TEAM-Q1-2021-Shareholder-Letter.pdf.
For everyone looking for alternatives the best site I have seen is https://bye-bye-server.com/.
C'est la vie. Bonne chance.
Sorry to hear that you will stepping away from being a community leader. I wish you well in your future endeavors.
Since Atlassian's announcement (some time ago now), I have worked to determine if migrating to Atlassian Cloud products is a viable option for our organization. This has taken time, and I think we have explored this reasonably thoroughly.
Our current conclusion is that it is not practical to migrate from Server to Cloud because:
As others have already noted - this decision seems to be in direct conflict with Atlassian 'policy' to not screw the customer. There is no current reason we would migrate to Cloud.
The most logical path seems to be; continue using JIRA Server as long as it keeps running, and stop paying for support at the EOL. Whilst simultaneously hoping we can find and migrate to a product from another vendor.
We are a small organisation and DataCentre is cost prohibitive.
If that's how it plays out, it seems Atlassian would lose the most as a result of their announcement. How do the shareholders feel about the plan I wonder...
The calculator also asumes that the developers can not work if jira is down which is ridiculous.
For the Cloud products you get a SLA of 99.9% uptime ( https://confluence.atlassian.com/cloud/service-level-agreement-for-cloud-products-973486377.html ) which means the service can be down about 43 minutes every month without compensation which could cost you 36$ per user/per month (by the same ridiculous asumption that developers can not work during downtime) - or eat up you savings. And you only get the guarantee on the premium plan.
From our point of view, the effort to keep track with the legal stuff is also considerable. Atlassian can change its terms of use and its addon provider locations from one day to the other. We must keep track wither relocation and change of contract is ok. If not, we have to save data, pull them from the cloud and shut down our instance.
On our private Server, things are MUCH easier to check: Once during installation, that's it.
So in fact we would move support from our IT to our legal department (oh wait, we do not yet have one...)
Hi!
Any plans for the DC make a tier for 250 users ?
Sorry for my English.
We also have a 5000+ (JIRA, Confluence) users and cant move to cloud due to compliance reasons. Politics :(
I new a lot of organisaions in our country (Russia) wich cant move to cloud with same reason (gov, med, a part of education...). And DC prices also is inaccseptable with our budgets. :(
Currently in our forums, chats and other a lot of discussions about alternative solutions to Atlassian product.
Atlassian Team, any news on the Server Champions group you said you were going to make?
hi @Alex Janes ! We actually updated the content of this very post with the links to the groups a couple of weeks ago. Please check the original post and you'll see the links to request access!
The Reliability and Performance group is open. For the other 3, if you are interested in participating, please request access and you'll get a response within 24 hours.
Hi Atlassian, especially Mr. Farquhar and Mr.Mike Cannon-Brookes.....
You have taken jobs from us, small companies around the world. We have helped your Atlassian to grow....
If you still think we will give our customers and our time to your cloud, you are wrong....
We need jobs, we need work and here is first example what will happend:
And we will remember ATLASSIAN, how "Don’t #@!% the customer" .... (no comment)
Recently I found a incident after which Atlassian temporary stops the multiple services. Refer below link for more details.
https://developer.status.atlassian.com/incidents/jg83t3n3cw5q
The respective services are not available from 15th March 2021. If Atlassian fails to protect his own data then how can we expect that they will protect our data after moving to cloud.
After this incident I am not going to trust the Atlassian Cloud service anymore.
Well played Atlassian.
While I agree that a great level of trust is required for the cloud solutions, I also believe that your conclusion is too harsh. Mistakes can always happen, it is unrealistic to expect that nothing ever should go wrong. The same rule applies to self-hosted solutions, btw.
If mistakes can always happen, what we should expect is
I think Atlassian did well in most of these expectations, except probably in the first, because it obviously took them three days to react to the first report. Something they must address after they have dealt with the current situation.
Metin, the only thing we can be sure about software is that it will contain bugs. Mistakes happen.
But I assume that server users all have thought about securing their Jira instance according to their individual security requirements. They may allow direct access via internet, trusting Jiras user authentication. They may restrict access to company local users (via Firewall/VPN), or even further down.
AFAIK the cloud based solution must be a "one size fits all". Atlassian determines the level of security available. If it fits, ok. If it doesn't fit, well, ok and bye.
One problem will be: What is the level of security Atlassian really offers? And will it still be there with the next update?
@Metin _savignano software solutions_
I totally agree with you. We are all human and make mistakes at some point in our lives.
But such a mistakes impact our business or most important data loss. The thing which we can not compromised.
The majority of our customers are small companies for whom data is important.
That is why we prefer on-premise and prefer to monitor our own security rather than relying on Atlassian for this.
We don't have any problem that Atlassian is promoting Cloud. They are preparing to drop the on-premise version, which is a concern for us.
サーバー製品の愛好者には、日本人もいることを忘れないでください。
クラウドへの強制移行は良くないと思います。同じ金額で同じサービスを受けられないことが理由です。
クラウドへの移行は決定事項かと思いますが、再度検討して頂くと助かります。