Hacker News Reader

Comment by orand | Hacker News Reader

Which Jira and Confluence features aren't available for fully upgraded self-hosted instances?

Not to beat a dead horse about it, but Atlassian made improvements to the Kanban functionality, especially regarding the backlog (a backlog manager), and didn't make it available to our on-premise locally-installed stuff.

Additionally, they jacked up the prices on the Service Desk software users and changed who can do what at what prices.

All in all, I wouldn't choose Atlassian for any new installations/companies. I would definitely look elsewhere. And, I've been using their products since before FishEye was an Atlassian product (and they destroyed that product too).

Ouch (and self-hosted atlassian products were pricy to begin with). Are there any good alternatives to Jira and Confluence out there (that are self-hosted/on-prem)?

I'm of the opinion that there are no good ticketing systems. I've seen a fair few of them (but haven't looked in the last year or two) and I realised that the problem is this: the amount of information you need to store to make a ticketing system really useful is more than people are comfortable putting in. Lightweight ticketing systems are great for small things, but suck for serious work. Heavyweight ticketing systems are a grind to use. Assigning metadata is tedious, remembering workflows is tedious, but if you want more power, you have to do those tasks, regardless of the particular software in use.

This is why I've finally accepted the fact that for my own personal tracking, nothing beats a post-it note. I'm not going to spend the time to put down all the real information I should and dealing with an app is another barrier preventing me from getting stuff done.

I moved to post-its about six weeks ago during an intense period with lots of small jobs. I am the only one who does what I do here, so the interoperability isn't really required... and I'm not keen on going back to a digital ticketing system (post-its are also satisfying to scrunch up when finished). I will eventually though, as ticket history can be useful, but at the moment I feel a bit like a dog who has escaped the yard and is roaming freely :)

> Assigning metadata is tedious, remembering workflows is tedious, but if you want more power, you have to do those tasks, regardless of the particular software in use.

This is why you hire dedicated Scrum Masters / PMO, and direct the PMOs to automate away what they can, as the domain becomes clearer.

Jira is actually really great for this because the REST API is so powerful, which can allow the PMOs to build systems which extract work from elsewhere, populate all the necessary fields which are repetitious and tedious for users to fill out, and then submit everything against the REST API and watch it all turn into issues.

When you start to understand that what Atlassian really did with Jira was build a powerful general UI abstraction over relational tables that even non-technical users can use, then you start to understand the sheer power of what's on the table.

Seconding this. It always seemed to me that you lose features by going to the cloud hosted version.

Reply on news.ycombinator.com