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

Atlassian Acquires AgileCraft for $166M

techcrunch.com

Post reply on HN
Print view View original

41–50 of 80 posts

Re: Atlassian Acquires AgileCraft for $166M

#41

Post by nisa »

sytse wrote: post #33
nisa wrote: post #8

Earlier quoted context omitted.

They just don't seem to care. You research something - after hours you'll end up at their bugtracker, where you can read the desperation of others (often some issues are not fixed in 10+ years). I don't understand their priorities. There is to date still no way to restrict visibility of work-logs on issues - a usecase basically every smaller shop has because the client is often participating directly in the JIRA. Ser…

You mean we're not going after Confluence or JIRA? Wikis are certainly not a priority for us. I think if you don't separate the proposer from the person who accepts the proposal the wiki tends to grow stale. So we're betting on static websites with GitLab Pages. There is a large market for wikis but you would have to use something easier than markdown, which is hard for us to get away from. We're going after JIRA. In…

Ohh, I really have to stop making snarky comments here :)

So I actually looked at migrating to Gitlab due our JIRA pains but it's not really possible if you have some already grown setup (it's not exactly easy to solve so no blame to Gitlab here)

- no JIRA import (it's possible with some REST-API fighting), but something easy would be nice: https://gitlab.com/gitlab-org/gitlab-ee/issues/2780

- The work-log issue is not solved as far as I understood the documentation, it's possible to have external users to hide internal projects but once you are on a project time-tracking information is visible.

- From a quick glance over the docs it looks like reporting on tracked time is also not possible out of the box - and probably not across projects - we use Tempo Timesheets on JIRA for that, the slash commands /spend /estimate are probably okay for devs but we also have other users that can deal with the fields in JIRA.

- It looks like the whole custom fields on issues is still in the works (we use that quite heavily) and there is no concept of workflows (we also have some custom setup there)

- Servicedesk looks neat through.

Don't get me wrong - this reads like: I want all JIRA features in Gitlab - maybe that's a stupid idea, for a new project I'd probably just use Gitlab and see how are I come.

Re: Atlassian Acquires AgileCraft for $166M

#42

Post by nisa »

jordanpg wrote: post #36
keithnz wrote: post #7

I've been really unimpressed with atlassian over the last few years. We started with bitbucket before it was acquired, it was super robust, then once atlassian got it slowly small bug after small bug kept making it into production creating mini headaches and they never seem like its super important to them. We also have Confluence, which is okish, but again, small bug after small bug keeps creeping in, like at the mo…

Atlassian software clears the good enough bar for me, functionally. But it’s all _so slow_. Every action in the cloud UI takes 2 seconds. I would prefer any other product that was snappier.

We run JIRA + Confluence on a dedicated server and it's good enough for us - give the JVM enough memory (4-8GB) and use HTTP/2.

Re: Atlassian Acquires AgileCraft for $166M

#43

Post by jacques_chester »

freddie_mercury wrote: post #40
jacques_chester wrote: post #29

Earlier quoted context omitted.

It looks to be a lightly-edited press release. Very common for journalists in a hurry to make quota or get the first link up.

It may be common for other journalists but I don't think that's the explanation in this case. Every acquisition I've been part of, we've briefed journalists beforehand (almost always someone at Techcrunch), they were under an embargo, and the article was pre-written.

> a service that aims to help enterprises plan their strategic projects and workstreams. The service provides business leaders with additional insights into the current status of technical projects and gives them insights into the bottlenecks, risks and dependencies of these projects.

These are not words I would expect a journalist to spontaneously generate. This is presser fluff.

Re: Atlassian Acquires AgileCraft for $166M

#44

Post by jbergstroem »

sytse wrote: post #33
nisa wrote: post #8

Earlier quoted context omitted.

They just don't seem to care. You research something - after hours you'll end up at their bugtracker, where you can read the desperation of others (often some issues are not fixed in 10+ years). I don't understand their priorities. There is to date still no way to restrict visibility of work-logs on issues - a usecase basically every smaller shop has because the client is often participating directly in the JIRA. Ser…

You mean we're not going after Confluence or JIRA? Wikis are certainly not a priority for us. I think if you don't separate the proposer from the person who accepts the proposal the wiki tends to grow stale. So we're betting on static websites with GitLab Pages. There is a large market for wikis but you would have to use something easier than markdown, which is hard for us to get away from. We're going after JIRA. In…

At my clients, they swear by jira workflows (that's the name, right?). The mindset of "customize everything" seems to be impossible to impact. A strong second is managerial heaven plugins with unlimited ways of clicking and visualizing other peoples clicks. Not sure how to compete with that; it's basically disagreeing about the curvature of the earth.

Re: Atlassian Acquires AgileCraft for $166M

#45

Post by dillera »

jedberg wrote: post #12
nisa wrote: post #8

Earlier quoted context omitted.

They just don't seem to care. You research something - after hours you'll end up at their bugtracker, where you can read the desperation of others (often some issues are not fixed in 10+ years). I don't understand their priorities. There is to date still no way to restrict visibility of work-logs on issues - a usecase basically every smaller shop has because the client is often participating directly in the JIRA. Ser…

> Confluence lacking some robust text-only markup (like markdown or asciidoc or whatever) The really irony here is that it used to have that! That was the only way I edited Confluence docs back in 2012 (and before) until they took the feature away. For a while you could dig into it, but pretty much any change you made not using the WYSIWYG editor broke the whole page.

I still run the Confluence 3.5 version (off the open net). The WYSIWYG runined Confy. It's an awesome, easy, fast wiki if you just stay at 3.5. And you edit it all in text.

Re: Atlassian Acquires AgileCraft for $166M

#46

Post by freddie_mercury »

jacques_chester wrote: post #43
freddie_mercury wrote: post #40

Earlier quoted context omitted.

It may be common for other journalists but I don't think that's the explanation in this case. Every acquisition I've been part of, we've briefed journalists beforehand (almost always someone at Techcrunch), they were under an embargo, and the article was pre-written.

> a service that aims to help enterprises plan their strategic projects and workstreams. The service provides business leaders with additional insights into the current status of technical projects and gives them insights into the bottlenecks, risks and dependencies of these projects. These are not words I would expect a journalist to spontaneously generate. This is presser fluff.

You seem to still believe that Techcrunch is journalism? I thought everyone learned a decade ago that it is a PR content farm thinly masquerading as journalism.

Almost certainly the journalist for this is known to someone on the Atlassian media relations team[1], assured them friendly coverage in (unstated, quid pro quo) exchange for future access and exclusives, and then the PR team provided them some copy as "background" for the article.

[1]: We can check this guess by looking at his previously publications about Atlassian:

- He announced the "next generation of hosted Jira Software"

- He announced new & improved integration between Jira & Github

- He announced the acquisition of OpsGenie

- He announced the launch of Bitbucket Pipelines

He's almost certainly been "friendly" with Atlassian marketing for at least 5 years, based on his publication history. So they call him whenever they have something new to announce and he publishes some click bait. It is win-win. After all, this is the article that made it the front page of HN...not any other article about the acquisition.

Re: Atlassian Acquires AgileCraft for $166M

#47

Post by jacques_chester »

freddie_mercury wrote: post #46
jacques_chester wrote: post #43

Earlier quoted context omitted.

> a service that aims to help enterprises plan their strategic projects and workstreams. The service provides business leaders with additional insights into the current status of technical projects and gives them insights into the bottlenecks, risks and dependencies of these projects. These are not words I would expect a journalist to spontaneously generate. This is presser fluff.

You seem to still believe that Techcrunch is journalism? I thought everyone learned a decade ago that it is a PR content farm thinly masquerading as journalism. Almost certainly the journalist for this is known to someone on the Atlassian media relations team[1], assured them friendly coverage in (unstated, quid pro quo) exchange for future access and exclusives, and then the PR team provided them some copy as "backg…

Are we angrily agreeing? Because I feel like we're angrily agreeing.

Re: Atlassian Acquires AgileCraft for $166M

#48

Post by applecrazy »

sytse wrote: post #33
nisa wrote: post #8

Earlier quoted context omitted.

They just don't seem to care. You research something - after hours you'll end up at their bugtracker, where you can read the desperation of others (often some issues are not fixed in 10+ years). I don't understand their priorities. There is to date still no way to restrict visibility of work-logs on issues - a usecase basically every smaller shop has because the client is often participating directly in the JIRA. Ser…

You mean we're not going after Confluence or JIRA? Wikis are certainly not a priority for us. I think if you don't separate the proposer from the person who accepts the proposal the wiki tends to grow stale. So we're betting on static websites with GitLab Pages. There is a large market for wikis but you would have to use something easier than markdown, which is hard for us to get away from. We're going after JIRA. In…

The service desk feature is nice, but maybe having a form for people to fill out to file a support request would be even better. That way, people can file requests without directly opening their email client.

Just a small thought :)

Re: Atlassian Acquires AgileCraft for $166M

#49

Post by freddie_mercury »

jacques_chester wrote: post #47
freddie_mercury wrote: post #46

Earlier quoted context omitted.

You seem to still believe that Techcrunch is journalism? I thought everyone learned a decade ago that it is a PR content farm thinly masquerading as journalism. Almost certainly the journalist for this is known to someone on the Atlassian media relations team[1], assured them friendly coverage in (unstated, quid pro quo) exchange for future access and exclusives, and then the PR team provided them some copy as "backg…

Are we angrily agreeing? Because I feel like we're angrily agreeing.

I'm not angry. Are you angry? Let's sing kumbaya till no one is angry.

Re: Atlassian Acquires AgileCraft for $166M

#50

Post by abrookewood »

keithnz wrote: post #7

I've been really unimpressed with atlassian over the last few years. We started with bitbucket before it was acquired, it was super robust, then once atlassian got it slowly small bug after small bug kept making it into production creating mini headaches and they never seem like its super important to them. We also have Confluence, which is okish, but again, small bug after small bug keeps creeping in, like at the mo…

I think the Devs are too busy writing JavaScript libraries. Annoyed at how slow Jira has become, I opened up Dev Tools and checked what was happening: the page size was nearly 30MB! Sure a lot of this is cached, but it's still insane.
Post reply on HN