Hi,
I'm developing Jira Addon in AngularJs 7. I'm facing two issues.
The first one is that I have added routing in my Addon it's is working fine on localhost but not working on Jira Live platform.
2nd Issue is that I'm getting 6200 records by using Jira Rest API. Jira is not allowing me to fetch more than 100 records per API call so I divided single API call into 62 API calls. The Problem I'm facing is that it's giving me error after 50 API Calls.
Please help me in this regard.
1. The Live environment probably have a proxy in front of it, something like nginx. That could explain the difference in behavior between local and live.
2. No way we can help you without any error logs. I'd recommend that you dynamically load the 6200 records and not try to load all of them in one shot. Maybe try paginating, so you load only the one shown and load the remaining when the user change pages.
Thank you, David for your Response.
1. I will look into it and will see how I can resolve it by using your recommendations
2. Pagination is already applied but the problem is we are showing some total values on the first page that are based on whole 6200 records.
Here's the screenshot of my console log https://prnt.sc/p207fq
Total records are 6200, I divided into 62 API calls. The first 50 API calls work fine on 51st API call it shows us this error.
Failed to load resource: the server responded with a status of 429 ()
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HTTP 429 means too many requests, so it seems to indicate you're hitting some kind of rate-limitation system.
I don't think JIRA has rate-limitation out-of-the-box, so i'd definitely look at a proxy in-front of your JIRA that would explain your problem, and why you don't have that same issue locally.
Let me know!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.