They just announced GA of agentic assignees. It suggests a year or more of maturation. Rovo Dev has already been a thing.

The Java products are almost EOL.

They have already been assigning JAC tickets to Rovo and $TEAM is down.

What else should be done with the surplus headcount?

▲

MeetingsBrowser 4 hours ago | parent | next [-]

My point exactly. This implies atlassian is not a healthy growing business, but a stagnant or even shrinking one.

Layoffs have little to do with AI, and more akin to fuel being jettisoned to stay in the air longer.

	▲	recursive 2 hours ago \| parent \| next [-]
		Must a business grow to be healthy? What about stability and longevity?
	▲	itomato 2 hours ago \| parent \| prev [-]
		Prioritization and workforce realignment. Old hat. Replacing headcount with technology? Also old hat. If the cuts ate into the good parts of the business, I will worry. I doubt that happened.

▲

jayd16 3 hours ago | parent | prev | next [-]

Can someone fix the damn Slack plugin so it stops asking me to turn it on every time someone posts a Jira link? I have dozens of messages from the plugin saying "Got it! Will not ask you again."

▲

stingraycharles 5 hours ago | parent | prev [-]

Are you making the argument that Atlassian’s products are basically done, no more development needed?

	▲	itomato 2 hours ago \| parent \| next [-]
		The Java ones have been done since version 6 or so. We’re up to what, 11? Stagnant, yes. Mature also.
	▲	gib444 3 hours ago \| parent \| prev [-]
		Right! There is more performance to be taken away yet! They're nearly there but plenty is left. Jira can be made "let's go brew coffee and come back" slow if the really tried