# Bug JIM-103 - Enabled rate limiting on Jira instance breaks projects selector.

Project: Stream Jira to OpenProject data Migrator
Status: closed
URL: https://community.openproject.org/work_packages/JIM-103

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 17.5.0 |
| Observed in versions |  |
| Sprint | Sprint 2 (within the cycle of 17.6) |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### 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 &quot;browsable&quot; 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 limiting error is not suppressed and communicated to a user with an action advice.
    

###
