Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian prepares to abandon on-prem server products

theregister.com

Post reply on HN
Print view View original

51–60 of 205 posts

Re: Atlassian prepares to abandon on-prem server products

#51

Post by john_cogs »

wdfx wrote: post #41
preisschild wrote: post #37

Earlier quoted context omitted.

Not OP, but we moved to Gitlab Issues. Project Managers are missing some features, but the devs (including me) like it a lot more due to integrating so well with PRs/commits.

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

Re: Atlassian prepares to abandon on-prem server products

#52

Post by petercooper »

raghavankl wrote: post #7
petercooper wrote: post #4

Earlier quoted context omitted.

37signals is certainly looking in the other direction: https://once.com/ .. though more at the smaller end of the market, not enterprise apps.

But they have also announced that Basecamp will always be a subscription product, which doesn’t fit well with their once.com story.

Can't imagine it's good business to scare the existing customers away.. ;-)

But yeah, I think this is more dipping a toe into the water. They seem to be focusing on entirely new products with a reasonable small scope. It's interesting to see it happen, though, and they're moderately influential.

Re: Atlassian prepares to abandon on-prem server products

#53

Post by imp0cat »

peanball wrote: post #43
wdfx wrote: post #41

Earlier 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?

There are issues at group / org level in GitLab that can span such tasks.

Also, you can create a special project to keep general issues (and use CI in this project to run Gitlab Triage bot to help you with issue management).

Re: Atlassian prepares to abandon on-prem server products

#56

Post by brobdingnagians »

kwanbix wrote: post #33
HHad3 wrote: post #12

Using 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?

YouTrack by Jetbrains is very good

Re: Atlassian prepares to abandon on-prem server products

#57

Post by rpy »

kwanbix wrote: post #33
HHad3 wrote: post #12

Using 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?

Linear is awesome

Re: Atlassian prepares to abandon on-prem server products

#58

Post by brightball »

preisschild wrote: post #37
kwanbix wrote: post #33

Earlier quoted context omitted.

While Jira does many many things right, it is also horrible in so many ways. What options are you evaluating?

Not OP, but we moved to Gitlab Issues. Project Managers are missing some features, but the devs (including me) like it a lot more due to integrating so well with PRs/commits.

Project Managers might just need some training. The board system in GL is very flexible and adaptable to how your org works.

I was really impressed.

Re: Atlassian prepares to abandon on-prem server products

#59

Post by ijustlovemath »

It's not the best for big organizations, but I've been quite happy with Gitea ever since the Gitlab pricing changes. Tons of features, rapid development, painless backup and upgrade process, and most importantly, very inexpensive to self host. If your team is in the low teens to low hundreds of people, it might already support your workflows!

Re: Atlassian prepares to abandon on-prem server products

#60

Post by neovive »

HHad3 wrote: post #12

Using 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 knowledgebase/documentation tool and less for collaboration. With our on-prem license expiring, we are migrating to a dedicated knowledgebase for our FAQ and frequently changing content and switching to a Markdown tool + Git for our more formal documentation.

Post reply on HN