Welcome to the Atlassian developer community @NanMu,
Since this thread has gotten pretty long, you may have missed that Jira Cloud’s rate limiting strategy is now documented.
To summarize, lets start with this statement in the docs:
The implementation of rate limiting is centered around tracking the cost of processing requests against various cost budgets.
This is another way of saying the rate limits are not a fixed number, but dynamic depending on some opaque measures of computing cost on the back-end. As a result, clients should pay attention to rate limiting headers and use a request backoff strategy.
We are aware this is not ideal for clients. While we do want to make improvements, as of writing this post no work has been scheduled nor any releases imminent. As such, I’m locking this thread to avoid further confusion. Since opaque limits may lead to further questions, please start a new thread and follow the advice on: