-
Bug
-
Resolution: Tracked Elsewhere
-
High
-
17
-
Severity 3 - Minor
-
5
-
| Update |
|---|
| An optimisation change has been implemented for the Two Dimensional Statistics gadget. Individual requests will now do some caching, this hopefully will reduce the amount of calls to the asset endpoint and reduce some rate limiting. There is a new ticket to optimise the rate limiting for asset objects api, and it's being tracked here: https://jira.atlassian.com/browse/JSDCLOUD-14247. |
Issue Summary
When using the Two-Dimensional Filter Statistics gadget in a Jira Dashboard, excessive requests are made to the /api/v1/object/bulk endpoint for each row and column that is an asset custom field, even when these fields are hidden. This behavior results in a high number of API calls each time the dashboard is refreshed, leading to surpassing the rate limit of 500 requests per minute. This consequently causes loading issues with Assets fields on tickets, as the fields fail to load and display an error.
Steps to Reproduce
- Add a Two-Dimensional Filter Statistics gadget to a Jira Dashboard.
- Configure the gadget to include asset custom fields in rows or columns.
- Refresh the dashboard.
Expected Results
The gadget should function without causing rate-limiting issues on the /api/v1/object/bulk endpoint. Asset fields on tickets should load without errors.
Actual Results
Excessive requests are made to the /api/v1/object/bulk endpoint, surpassing the rate limit and causing loading issues with Asset fields on tickets.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSDCLOUD-14247 Utilizing experiences with Assets object fields surpasses API rate limits and fields/SLAs loading errors
- Gathering Interest
- is implemented by
-
DAG-1039 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-