Sounds like „Prepare to abandon Atlassian products“
Atlassian prepares to abandon on-prem server products
61–70 of 205 posts
Re: Atlassian prepares to abandon on-prem server products
#62Earlier quoted context omitted.
The problem with this though, is that commonly a requirement (ticket) does not map exactly to a single code repository. I feel that it is breaking encapsulation in a sense to be dealing with issues at the repo level. The repo and the code are implementation details of the business requirements. The tickets describing requirements belong at the next level up of abstraction?
GitLab team member here. One way to approach this would be using Epics [0], which can live at the group-level. Child epics and/or issues can then be used for more finely tuned requirements. 0 - https://docs.gitlab.com/ee/user/group/epics/index.html
I should point out that multi-level epics are only available at Gitlab's $99 per user per month level. We wanted to use them, but it's not worth that much. Jira is a lot more flexible and cost effective in this regard.
Re: Atlassian prepares to abandon on-prem server products
#63Atlassian Data Center edition will continue to be supported. It is the same software as the Server offering but with a different product key unlocking some more features like multiple nodes. It is far more expensive than Server, but still cheaper than Atlassian Cloud. And I found the per-user pricing to be about on par with alternative products from other suppliers. But for small companies, the brittleness of the licence count tiers can really inflate the cost.
Re: Atlassian prepares to abandon on-prem server products
#64Using Atlassian cloud products is a business risk. They previously let customers sit for weeks without access to their data [1]. Cloud-hosted products do get early patches for unsecured /setup routes though [2], so there's that. At this point the decision has been made in our org to firewall their products off the internet and internal networks, and migrate to something else by 2024. [1] https://hn.algolia.com/?q=atl…
While Jira does many many things right, it is also horrible in so many ways. What options are you evaluating?
Slab is an excellent replacement for Confluence, although it doesn't help with Jira.
Re: Atlassian prepares to abandon on-prem server products
#65Why would they continue with on-prem? It has to be a support nightmare.
Re: Atlassian prepares to abandon on-prem server products
#66Using Atlassian cloud products is a business risk. They previously let customers sit for weeks without access to their data [1]. Cloud-hosted products do get early patches for unsecured /setup routes though [2], so there's that. At this point the decision has been made in our org to firewall their products off the internet and internal networks, and migrate to something else by 2024. [1] https://hn.algolia.com/?q=atl…
We're in the same boat. I brought Confluence into our org almost a decade ago — it was the best collaborative wiki tool at the time. Over time the price has increased while the quality of the tool has not kept pace with other options. This seems to be the trend as software companies grow into large "enterprise" providers. Looking at our Confluence usage over the years, I noticed that we use it primarily as a knowledg…
Could you share what markdown/git tooling you've identified?
Re: Atlassian prepares to abandon on-prem server products
#67Using Atlassian cloud products is a business risk. They previously let customers sit for weeks without access to their data [1]. Cloud-hosted products do get early patches for unsecured /setup routes though [2], so there's that. At this point the decision has been made in our org to firewall their products off the internet and internal networks, and migrate to something else by 2024. [1] https://hn.algolia.com/?q=atl…
While Jira does many many things right, it is also horrible in so many ways. What options are you evaluating?
We've moved to plain markdown in Git(Lab) as Confluence replacement. A CI pipeline compiles it to HTML and hosts it on the web via Material for MkDocs.
It lacks most collaboration options for non-developer users, but we found that they are rarely, if at all, used anyway. Non-developer users can still use an edit button that points to GitLab's web editor and update the docs that way.
I can't suggest a replacement for Jira at this point. I don't think there is one tool to recommend that fits every company's workflow. The other comments seem to have some nice tools to try.
Re: Atlassian prepares to abandon on-prem server products
#68This is misleading because you can still buy the data center version which replaced the server version.
Re: Atlassian prepares to abandon on-prem server products
#69Jira/Confluence are two products that have gotten markedly slower and slower over time and as they've moved into the cloud. I observe load times that remind me of the 90s sometimes using their cloud apps. Incredible they are killing on-prem, but maybe it makes it harder to compare to the slow as molasses cloud offering that way?
On prem is not being killed. They still have the data center products
"To be clear, we have no plans to end of life or end of support for our Data Center offering."
https://community.atlassian.com/t5/Data-Center-articles/The-...
Re: Atlassian prepares to abandon on-prem server products
#70Earlier quoted context omitted.
I have the opposite experience; many if not most of the features have gotten faster as the features have expanded in capability
Same. On-prem at my last employer was super slow. Cloud is wildly fast.
I have used a cloud instance that had too much data, and ran very slow.