Now, that’s a base number - you need to modify it further based on the following questions:Ĭan you afford to interrupt your users’ work? If your users’ integrations are mission-critical, consider upgrading your hardware instead. Since UI traffic is not rate limited, this number will be higher than what you need as your rate limit. You can do this by parsing the access log and finding a user than made the most REST requests over a day. The first step is to understand the size of traffic that your instance receives.
Setting the right limit depends on many factors, so we can’t give you a simple answer. It really depends on the app, but we’re assuming most of them shouldn’t be limited. An app like that sends external requests and behaves just like a user sending requests over a terminal. and then reshuffles and displays them in its own way as the earlier mentioned wallboard. It asks Jira for details about boards, issues, assignees, etc.
Let’s say we have an app that displays a wallboard on TV. Traffic like that would be internal, not limited.Įxternal: Apps whose requests are external to Jira are limited. Let’s say this banner checks all issues that were done and shows this sprint’s winner - a user who’s completed the most issues in this sprint. An example of such app would be a special banner that’s displayed on a Scrum board. Internal: If an app in fact works internally, enhancing the user experience, it won’t be limited. But, as always, it depends on how an app works. The general assumption is that Marketplace apps are installed on a Jira instance, make internal requests from within Jira, and shouldn’t be limited.