@AlanBraun – Thank you for the additional context and for acknowledging the gaps in the initial communication. It’s reassuring to hear that enforcement in February is expected to be a non-event for the vast majority of partners.
That said, my concern is less about February itself and more about what happens on any ordinary day after enforcement begins.
Specifically: what will happen when an app exceeds Tier 1 limits?
I understand Atlassian’s commitment to working closely with partners, but there’s an important gap between identifying an issue and resolving it. During that window, what should partners and customers expect?
-
Will the app experience 30+ minute outages?
-
What’s the order-of-magnitude time-to-resolution? Minutes, hours, days, or weeks?
-
What does “proactively partnering” look like in real time for customers already in production?
To make this concrete, here’s a hypothetical scenario.
New Enterprise usage on a Tier 1 app
Imagine a Jira Cloud reporting app (let’s call it “Super Awesome Business Reports”). It’s relatively new, has a modest SMB customer base, and is operating comfortably within Tier 1.
An Enterprise customer (let’s call them ”Acme Enterprise, Inc.”) begins a Jira Data Center → Cloud migration. Acme needs a new reporting app, because their custom home-grown reports won’t migrate to Cloud. They find Super Awesome Business Reports in the Marketplace and install it in an Enterprise sandbox.
Now they want to evaluate whether the app will meet their needs, so they run a large exploratory report, perhaps across 1+ million issues.
What happens next?
-
For the prospective Enterprise customer: Does the app function reliably during this evaluation, or is it likely to hit Tier 1 limits during a perfectly reasonable “trial” use case?
-
For existing paying customers: Are they insulated from this spike, or do they experience outages because of activity in Acme’s enterprise sandbox?
-
For the vendor: Is there a realistic path to winning the Enterprise customer? Or is their best-case scenario simply not losing existing customers during the outage(s)?
From the outside, it’s not clear how Tier 1 handles this kind of legitimate-but-sudden usage without creating cross-tenant impact.
Another scenario: Connect → Forge migration under the new limits
Now consider the same app, but as an established Connect app migrating to Forge. The vendor is already dealing with:
Under the new model, they also need to accurately predict their future API point consumption before deploying to production and hope they qualify for Tier 2 in advance.
If that estimate is wrong (or if Tier 2 is declined), the result isn’t just throttling. It’s production instability for existing customers in validated or business-critical environments.
I trust Atlassian has thought through scenarios like these, but I haven’t yet seen them clearly addressed in the “95% non-event” framing. For partners and customers, especially customers in enterprise and regulated contexts, these edge cases are exactly where confidence is won or lost.
It would be extremely helpful to understand:
-
How sudden, legitimate spikes from a single tenant are handled in Tier 1
-
What protections exist for other tenants during that period
-
What the expected time-to-resolution looks like once an issue is detected
Greater transparency here would go a long way toward helping partners and customers assess risk and plan responsibly.
Thank you for continuing to engage on this.