3 ms·

I don't see why anyone couldn't unseat Atlassian. JIRA and Confluence are moderately difficult problems to solve, but it's not impossible to create a lean compe

I don't see why anyone couldn't unseat Atlassian. JIRA and Confluence are moderately difficult problems to solve, but it's not impossible to create a lean competitor with a small team and some funding. Winning the war will be identifying a reason for companies to switch. There has to be something particularly painful enough with existing solution to help facilitate conversion. On the opposing side: maybe it's an easier sell to know a business uses Atlassian tools (from a talent acquisition perspective). If you were hiring engineers and told them you used SVN instead of Git for version control, maybe it just makes the role less marketable. "Another tool I have to learn", one could think.

ianwalter 7y ago
It's been my experience that developers care much more about the user/developer experience than having to learn another tool but then again I've spent more time working in startups than I have working for large companies.
- JMTQp8lwXL 7y ago
  I've accepted the obviously flawed UI for what it is. Instead of being able to move an issue from one backlog to another via the Edit modal (where you can edit virtually every piece of information about the issue), you have to click the "More" dropdown, then "Move". I used JIRA for three years before I knew that. I hope somebody from Atlassian sees this comment.
Noumenon72 7y ago
Migrating Confluence Server to Confluence Cloud has taken so much time and support that it would take a strong company to handle migrating out. Of course there are specialists in this migration process, whom I maybe should have hired. As an engineer, I love Confluence, every business I've interviewed with has used it, and I'd be slightly worried about how a company survives without it. I don't care about Jira, except for how it works with Bitbucket.
- dreamcompiler 7y ago
  > Migrating Confluence Server to Confluence Cloud has taken so much time and support that it would take a strong company to handle migrating out. I just went through this and my major pain point was having to upgrade my server to 5.9 before the automatic migration tool would work. Hello? I'm moving to cloud because I don't want to have to do the upgrade process yet again. Now I have to upgrade a server I'm about to switch off. Oh, and manual migration with the XML export files just kind of silently fails, so you have no choice but to use the migration tool. Nice. Other than that, the important switches are buried four levels deep and the docs never describe the particular UI that's in front of me, but that's something I've learned to expect from Atlassian. Seems to have worked but it took a lot more futzing around than it should have.

ianwalter 7y ago

It's been my experience that developers care much more about the user/developer experience than having to learn another tool but then again I've spent more time working in startups than I have working for large companies.

JMTQp8lwXL 7y ago
I've accepted the obviously flawed UI for what it is. Instead of being able to move an issue from one backlog to another via the Edit modal (where you can edit virtually every piece of information about the issue), you have to click the "More" dropdown, then "Move". I used JIRA for three years before I knew that. I hope somebody from Atlassian sees this comment.

Noumenon72 7y ago

Migrating Confluence Server to Confluence Cloud has taken so much time and support that it would take a strong company to handle migrating out. Of course there are specialists in this migration process, whom I maybe should have hired. As an engineer, I love Confluence, every business I've interviewed with has used it, and I'd be slightly worried about how a company survives without it. I don't care about Jira, except for how it works with Bitbucket.

dreamcompiler 7y ago
> Migrating Confluence Server to Confluence Cloud has taken so much time and support that it would take a strong company to handle migrating out. I just went through this and my major pain point was having to upgrade my server to 5.9 before the automatic migration tool would work. Hello? I'm moving to cloud because I don't want to have to do the upgrade process yet again. Now I have to upgrade a server I'm about to switch off. Oh, and manual migration with the XML export files just kind of silently fails, so you have no choice but to use the migration tool. Nice. Other than that, the important switches are buried four levels deep and the docs never describe the particular UI that's in front of me, but that's something I've learned to expect from Atlassian. Seems to have worked but it took a lot more futzing around than it should have.