Hi Atlassian, I saw that you announced a new points-based rate limit system in CHANGE-2958 , which is going live in 48 days. This announcement leaves a number of things ambiguous and I am hoping that you can provide some clarifications: Previously, rate limits were documented as applying only to…

After testing the behavior of some Jira APIs I must say I am mostly confused with results rather than comforted. I observe two very different cost-related rules on different APIs for bulk requests: Points are calculated based on the type of API request and the objects affected. Each request start…

@AlanBraun / @ChrisHemphill1 , I guess I should not be surprised given Atlassian’ track record, but I still did not expect broken promises on such an important topic. [image] AlanBraun: We acknowledge that we could have done better in the amount of detail we provided upfront and the time availa…

I’ve performed some analysis based on the new rate limiting headers we’ve received and noticed that our Jira app reported that it’s on the global pool and has no points available. Afterwards, I saw the headers reporting again that our app is based on the per tenant pool again. Interestingly, this …

I tested the new points-based rate limits and observed behaviour that contradicts the Quick Reference Guide. The guide states: > **UI → @forgeforge/bridge.requestJira (no resolver / no backend call) (** Log in with Atlassian account ) > Treated as user-initiated UI traffic and not counted toward …

Atlassian is asking us to be ready for a system that is not yet fully ready on their side.

Yep, kinda expected. We want to know in advance what is happening, and they want feedback and are being agile (put it out. is that going to work. make changes. repeat) Giving us the general direction is all we can expect. It’s not bedded down because of legit complaints. Will they get it right, prob…

Hey Atlassian, Now that this change has been rolled out, I see some problems: Documentation incorrect for “RateLimit-Reason” The constants described in the docs for the RateLimit-Reason field do not match what is returned in real life, or at least not for Confluence. Can someone please fix the doc…

Thank you for sharing this @scott.dudley . Our Confluence apps use the exact same call. It is the only API we are aware of that can determine if a user has space admin permissions. Maybe Atlassian would consider adding a filter to this API by principal accountId or operation key before counting …

Hi @BurakAKTEPE I will review this with our team and circle back to this thread.

Hi @scott.dudley Quick response - We will fix the documentation, and I will review the point costs you highlighted and circle back.

2026 point-based rate limits

General

nathanwaters April 14, 2026, 12:55am 170

Atlassian: “new global pool limit for rate limiting”

Also Atlassian:

1 Like