Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Angular Routing not Working

uzair nazir
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 28, 2019

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 answer

0 votes
David Laperle
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 28, 2019

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. 

Mubashir Nazir
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 4, 2019

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 ()

David Laperle
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 5, 2019

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!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events