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

Atlassian Valued at $3.3 Billion

blogs.wsj.com

Post reply on HN
Print view View original

81–90 of 169 posts

Re: Atlassian Valued at $3.3 Billion

#81

Post by mzd348 »

lobotryas wrote: post #28
malanj wrote: post #8

Really cool that you can reach that kind of valuation with a basket of products, rather than a single run-away network effect fueled win. I find it very inspirational that they do that well by building great software that people love. also: They really make awesome products (we use BitBucket, HipChat and Confluence)

>great software that people love As someone who has to use and administer JIRA I'll have to respectfully disagree. The nicest thing I can say about the product is that it was built "by engineers, for engineers". People who want empowering software that gets out of the way appear to have been an afterthought.

JIRA has got an extremely "nervous" interface where clicking around in innocuous places (like blocks of text) causes strange things to happen, editing modes to be entered, and things to move around unexpectedly. So in this sense it "gets out of the way" nicely.

Re: Atlassian Valued at $3.3 Billion

#83

Post by stephengillie »

jeffsinclair wrote: post #47
stephengillie wrote: post #32

We've had a rough, shaky time using Jira, but it's almost entirely due to internal politics and constantly-shifting business priorities. (aka CEOs and owners who are just megaphones for their corporate customers) We intended to replace our invented-here ticketing system (which has Zendesk integration) with Jira, but instead we integrated Jira into that invented-here ticket system. On the other side, my team has been…

Check out http://answers.atlassian.com if you want to try and get some crowd-sourced answers to your problems! Happy to try and help resolve any sticking points you may have.

Thanks for the invitation, but the problem is 6 years old (https://jira.atlassian.com/browse/JRA-15964) and I don't know that there's a resolution in sight (https://jira.atlassian.com/browse/JRA-19091)

Re: Atlassian Valued at $3.3 Billion

#84

Post by [deleted] »

jeffsinclair wrote: post #53
sledmonkey wrote: post #42

Earlier quoted context omitted.

We had a similar bug that we worked around by adding a transition view of "Resolved Issue Screen" to all steps leading to done in the Add Workflow Transition page.

If you also want to fix existing issues, I'd suggest creating a "loopback" workflow transition on the resolved state, and adding a post-function that sets the resolution to "Fixed" or something similar. You can then bulk transition all your existing issues and the resolution will get populated correctly.

[deleted]

Re: Atlassian Valued at $3.3 Billion

#85

Post by latortuga »

polskibus wrote: post #61
eropple wrote: post #36

Earlier quoted context omitted.

> Yes, and they all suck. Redmine ain't bad.

I love redmine, it's been really good and 0 upkeep for my company for a couple of years now.

I hope you don't mean literally zero because there have been numerous Rails vulnerabilities in the intervening time. If you're been running the same instance for a few years unpatched and publicly accessible, chances are good your installation is owned.

Re: Atlassian Valued at $3.3 Billion

#86

Post by aeflash »

thathonkey wrote: post #48
hyp0 wrote: post #33

oblig. BitBucket has free private repo's https://www.atlassian.com/software/bitbucket/overview you don't get to 3 billion dollars without giving away a lot of stuff for free to infiltrate the enterprise

I use Github for personal stuff and Bitbucket at work. They're pretty comparable. I don't really have a problem with either. Some parts of the Bitbucket UI are nicer, some parts of the Github UI are nicer. It's hard to beat free private repos but note that they are limited to 5 users. If you have a larger team, you've got to pay.

Another key distinction of Bitbucket is that you pay per private collaborator, rather than per private repo. You could have a 5 person team but 100 private repos, and it would still be free. After that its $1 per user per month. With Github, the 50-125 private repo tier costs $100 per month for an organization.

Re: Atlassian Valued at $3.3 Billion

#87

Post by polskibus »

latortuga wrote: post #85
polskibus wrote: post #61

Earlier quoted context omitted.

I love redmine, it's been really good and 0 upkeep for my company for a couple of years now.

I hope you don't mean literally zero because there have been numerous Rails vulnerabilities in the intervening time. If you're been running the same instance for a few years unpatched and publicly accessible, chances are good your installation is owned.

Not my case. I didnt mean literally zero but we never hit a bug.

Re: Atlassian Valued at $3.3 Billion

#88

Post by nraynaud »

dudurocha wrote: post #67
nraynaud wrote: post #39

What would be the exit for the VCs? they could have kept it private without the VCs, but I don't think VCs line up for dividends at the end of the years. That forces them to create an exit event for a company that seems in a nice path.

IPO

I don't get the point of going public when you don't really need money. With the press trying to find sensational stories, the sheepish behavior of the markets etc.

Re: Atlassian Valued at $3.3 Billion

#89

Post by jeffsinclair »

stephengillie wrote: post #83
jeffsinclair wrote: post #47

Earlier quoted context omitted.

Check out http://answers.atlassian.com if you want to try and get some crowd-sourced answers to your problems! Happy to try and help resolve any sticking points you may have.

Thanks for the invitation, but the problem is 6 years old ( https://jira.atlassian.com/browse/JRA-15964 ) and I don't know that there's a resolution in sight ( https://jira.atlassian.com/browse/JRA-19091 )

This is fixable - I have done it myself. It's not possible to add an outgoing transition on an active (or draft of an existing active) workflow. So you work around this by:

* Create a copy of your workflow * Add the outgoing transitions that you want to add * Change the workflow scheme to point at the new workflow

It's not super elegant but if you need to work around it you can.

Feel free to connect with me on twitter (@jsinkers).

Post reply on HN