Content
View differences
Updated by Pavel Balashou 2 days ago
### Steps to reproduce
1. Enable rate limiting on Jira instance for a user to a really low value(e.g. 1 request per second, 1 total request)
2. Create a new jira import run
3. Fetch meta data
4. Then open project selector and see that some projects are not listed.
### What is the buggy behavior?
* During fetch meta data phase we expect every project to be "browsable" by the user. With enabled rate limiting some requests are getting blocked. Then these projects are considered unavailable for this user. When in truth they are available.
### What is the expected behavior?
1. Rate limited requests does not interfere with project browsablitiy check requests.
2. Rate limiting error is not suppressed and communicated to a user with an action advice.
###
1. Enable rate limiting on Jira instance for a user to a really low value(e.g. 1 request per second, 1 total request)
2. Create a new jira import run
3. Fetch meta data
4. Then open project selector and see that some projects are not listed.
### What is the buggy behavior?
* During fetch meta data phase we expect every project to be "browsable" by the user. With enabled rate limiting some requests are getting blocked. Then these projects are considered unavailable for this user. When in truth they are available.
### What is the expected behavior?
1. Rate
2. Rate
###