Jira API rate limiting

We – and many of our enterprise customers – are concerned about the upcoming changes to Jira API rate limiting and would like to clarify the following points:

  1. Scope of limits: Can you confirm that limits are applied per tenant (so tenant1.atlassian.net is tracked independently from tenant2.atlassian.net)?
  2. Options for increasing limits: What can we or our customers do to increase those limits? Particularly…
    1. Do higher subscription levels (e.g. Jira Premium vs. Jira Standard) and a higher number of users in a tenant imply a higher API rate limit?
    2. If we change our Jira app from free to paid, will that allow for a higher rate limit?
  3. Timing: When will those limits actually be applied? Is November 22 still accurate?

Any clarification you can provide would be greatly appreciated.

12 Likes

Similar questions here – would be great to answer those, too: Marketplace granular rate limiting