Introducing our new packaging model for Jira Cloud Automation

[Deleted user]

Hi

I conclude that if an automation is launched when the limit is reached, it will not succeed.

Eva

[The_Contractor]

@l.seplecan I'm glad you said

...or what is the position of the community members.

I suspect they (Atlassian) are looking at the $$ only (I.e., admins of Premium or Enterprise customers). And not appreciating that there are some of us who consult / advise many companies or give speeches that advise on trends. 

I alerted my team of consultants on Monday of what is happening. A few laughed as if they saw it coming. One stated "This is finally the death knell of a great thing. Had to happen at some point".

I'm waiting to see if there is any marked differences from the Atlassian messaging next week. If this freight train continues as it has by end of week, Atlassian will be pulled as our primary tool for Project / Development / Support / Documentation management solutions. 

Sad times.

[KC Wong]

We are merely a slab of meat on a cutting board. Non-enterprise users are tiny scraps of meat to be discarded. 

Atlassian can do a bait and switch with automation, they can do it with something else later. 

[KC Wong]

And this is what Jira Cloud looks like on a laptop: 

Thanks for the non-dismissable giant notification Atlassian. Now I have about 3cm of vertical space when I edit an automation rule.  

[Brock Jolet]

Atlassian: "Don't worry, your team should be fine with the new limits."
Also Atlassian: "Our new usage calculator shows that you've used 47% of your limit in 4 business days." 

[Emilson Margoto]

I've reached 100% of the limite before the end of the 2nd day... and I've received a confortable e-mail saying that all is under control, an upgrade wouldn't be necessary.  Who to believe in?

[Steven Rhodes]

Atlassian can change its mind it seems. They have reversed track on the decision to remove Jira Work Management licenses from Jira Software in March 2024. Not the best idea they ever had and this current automation decision has attracted more negative reactions than I've seen in recent memory.

Reversal page here:

https://community.atlassian.com/t5/Jira-Work-Management-Articles/Better-together-Jira-Work-Management-is-staying-included-with/ba-p/2489188

[Constantin Lotz]

I would suggest you open some tickets at the support. I've tried that too, but not yet received an answer (some days ago...)

[Haddon Fisher]

Is there a way to "re-trigger" the email from Atlassian about the projected utilization impacts? I see we should have gotten something around October 2nd, but it looks like neither myself nor the other admin on my instance got anything.

[Charlie Gavey]

@Brock Jolet @Emilson Margoto @Haddon Fisher If you didn't receive an email around your usage, or if the usage you're seeing in the Usage Tab doesn't appear to be consistent with the email around your previous usage, please do reach out via support so we can investigate.

[Srini Chakravarthy]

Hello Community,

We're happy to share that we've added Re-fetch issue and Lookup issues to the list of non-countable actions. With this update, we now have 5 actions that are not counted against the limit

1. Re-fetch issue

2. Lookup issues

3. Log action

4. Create Variable

5. Create lookup table

[KC Wong]

@Srini Chakravarthy 

Look at the prevous comments, people reaching the monthly limit in 1 or 2 business days, they must be crying tears of joy now. 

/s

[Steffen Helfenberger]

@Srini Chakravarthy 

lol. Thank you sooo much, you fixed our limits with this. Not!

Just change the policy: 60 automations per user in standard, 150 automations per user in premium (or unlimited). It's that easy.

This would be 2 automations per user per day in standard and 5 in premium. 

[Emilson Margoto]

Well... as I have been ignored by the support team (CA-2595939), and time is running fast, I started to analyse other tools to replace JSM. The board has approved my suggestion (Zoho Desk). Let's see what happens by November 2nd (my birthday, unfortunately). 

[Rune Rasmussen]

@Srini Chakravarthy If nothing else, it's nice to see the number of actions that won't count against usage increase. At least things will be a bit less shit. They will still be shit, but now a bit less.

A few other points of input.

With no signs of reverting course on this boneheaded decision, it would be really good if the usage overview could display usage trends of a day-to-day basis, rather than just a month.
We've made changes to our most "expensive" automations and need to monitor the usage to see if the change will help us skirt under the new limits.
Only having a monthly or month-to-date overview means that we have to make a note of the usage numbers every day, at the same time of the day.

And since Atlassian seems insistent on torpedoing the trust their customers have in them, are there any plans on increasing the total amount of allowed "components" in automations, or will it remain a meager 65?

And in continuation; are you considering/planning to add the "Send web request" action to the list of actions not counting towards usage?
With the limit of 65 "components" in an automation we've had to split up some automations.

[Alain Kovacs]

@Rune Rasmussen Thank you for that! Extremely valid points. The "Send web request" not counting would be like a godsend.

[KC Wong]

https://fortune.com/2023/10/10/unity-ceo-john-riccitiello-retires-video-games-engine-price-gauging-epic-unreal/

Hey Atlassian, Unity's former CEO John Riccitiello is looking for a new job. I think he will fit right in. 

[Alain Kovacs]

@KC Wong how to destroy your company 101

[Adam England]

What you say:-

"The new packaging model brings a simpler, more consistent way to measure Automation usage."

What you mean:-

"We just spent a billion dollars on a video company, help a brother out..."

[Lara Jones]

@Srini Chakravarthy  No one from support ever reached out to us. I sent a message and our other admin sent a message and support failed to respond to either one of us despite the fact that we both were addressing the complete stop of all automation. 

It was clear Atlassian intended for us to upgrade rather than offer any solution for the month of October.  

The likely outcome of this forced upgrade is that when our budgeting decisions are made next year,  Atlassian may be cut and we will be forced to another system.  

I'm not sure you've thought this through.  This is another one of those "short term gains" at the expense of long term growth.  

[Simone Hale]

After spending months convincing my company to use Atlassian to build out a new system using automations, all the people who pushed back owing to the subpar features and limits of Atlassian get to have their "I told you so" moment.
Absolutely shocked that after encouraging companies to use these tools, you implement limits.  
Short term gains at the expense of long term growth indeed.... 

Sadly I could never recommend this tool again

[Yatish Madhav]

Has anyone ever gotten a reply RE the fact that the preview usage only shows this month and last month? Not really useful

Again, I think as many others I would push this move ot next year or at last 3 months after this article was posted since it does a hard stop after 1 Nov which can break things ... 

I would also be more than happy for more Jira Software Standard automations since this is from unlimited to a mere 1700 ...

Thank you

[Brock Jolet]

If you’re on an annual Atlassian Cloud subscription and approve a valid annual quote dated prior to October 18th, 2023, limits in the new model will apply on the next renewal date.

I reached out to an Atlassian rep to get a quote for a yearly renewal weeks ago and he still has not provided the quote. I followed up last week and he said, "I should have it for you today." Now it's two days out from the deadline and I have nothing to show for it. I'm starting to think they are just baiting me until it's too late.

[Brandon]

..

[The_Contractor]

Update from my side after finally catching up with my fellows. 

Collectively we implemented or manage 47 different instances that are going to exceed limits. We all have raised Support tickets for each one, respectively. Results are as expected, poor.

Only 9 Support responses out of that, all giving the party line the OP states and told to upgrade if more runs are needed (despite a couple of those still exceeding premium limits).

That's 38 non-replies... Wow...

Firstly, scriprunner is saving our butts. Whew

22 of these customers have committed to leaving Jira asap. Some have even fast tracked signing of contracts.

5 have accepted scriprunner as a long term alternative.

14 will accept scriprunner for the next year while they figure out budgeting and plans for 2024, with a view to leaving Jira in 2024.

6 we are still waiting back to hear.

For those who work as an MSP consultant know that these last 2 buckets are a high risk that we too have lost customers.

There are 2 major mistakes on Atlassian's part here:

1. Giving us 6 weeks notice of changes to, in many cases, a critical line of business solution.

2. Making absurd structure changes in how the automation feature is billed.

On this last note, I get that compute costs are up, companies are hurting, so some kind of change could be accepted. But this structure is just bananas.

It's been a fun ~12yrs or so, thank you for the good times.