Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-14247

Utilizing experiences with Assets object fields surpasses API rate limits and fields/SLAs loading errors

XMLWordPrintable

    • 169
    • 78

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Hide

      Hello Team 👋

      We are committed to continuously improving our platform to better serve your needs and ensure the highest standards of performance and reliability. As part of our ongoing efforts to optimise your experience, we want to update you on important enhancements and future developments impacting our rate limits.

      Enhancing Assets Performance
      In response to feedback about our current rate limits, we are excited to announce significant investments in the performance and reliability of our Assets system for the 2024/25 period. These upgrades are designed to support higher capacity and more flexibility, allowing us to responsibly increase rate limits. Look out for a community post regarding our early access program, which will give you a sneak peek at these improvements.

      Introducing a New Dashboards Platform
      To further enhance your experience, our Dashboards team is developing a new platform that will integrate seamlessly with a data lake. This means fewer calls to Assets and, consequently, more breathing room within the rate limits. Please keep an eye for a community announcement about this exciting development from our dashboards team.

      We totally understand that the current rate limits may not fully meet everyone’s needs, but these intentional safeguards are in place to prevent potential downtimes and ensure system stability. While there is no immediate resolution, these initiatives are our top priority, and we are working diligently to implement these solutions as swiftly as possible.

      Thank you for your understanding and support as we enhance our platform. We are excited about the improvements underway and are looking forward to sharing more updates with you.

      Mohamed Hassan | Product Manager, JSM Assets

      Show
      Hello Team 👋 We are committed to continuously improving our platform to better serve your needs and ensure the highest standards of performance and reliability. As part of our ongoing efforts to optimise your experience, we want to update you on important enhancements and future developments impacting our rate limits. Enhancing Assets Performance In response to feedback about our current rate limits, we are excited to announce significant investments in the performance and reliability of our Assets system for the 2024/25 period. These upgrades are designed to support higher capacity and more flexibility, allowing us to responsibly increase rate limits. Look out for a community post regarding our early access program, which will give you a sneak peek at these improvements. Introducing a New Dashboards Platform To further enhance your experience, our Dashboards team is developing a new platform that will integrate seamlessly with a data lake. This means fewer calls to Assets and, consequently, more breathing room within the rate limits. Please keep an eye for a community announcement about this exciting development from our dashboards team. We totally understand that the current rate limits may not fully meet everyone’s needs, but these intentional safeguards are in place to prevent potential downtimes and ensure system stability. While there is no immediate resolution, these initiatives are our top priority, and we are working diligently to implement these solutions as swiftly as possible. Thank you for your understanding and support as we enhance our platform. We are excited about the improvements underway and are looking forward to sharing more updates with you. Mohamed Hassan | Product Manager, JSM Assets

      Issue Summary

      There are experiences which send excessive requests to the /api/v1/object/bulk endpoint. This behavior results in a high number of API calls, leading to surpassing the rate limit of 500 requests per minute. This consequently causes loading issues with Assets fields and SLAs on tickets, as the fields fail to load and display an error.

      One of the experiences that has this issue is the Two Dimensional Statistics gadget on Jira Dashboards.

      Steps to Reproduce

      1. Add a Two-Dimensional Filter Statistics gadget to a Jira Dashboard.
      2. Configure the gadget to include asset custom fields in rows or columns.
      3. 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

      Due to the way statistics works, it needs to load all the issues returned from a filter to calculate stats. Therefore unlike in other experiences, such as filter page or issue navigation page, where issues are paginated and only a small portion of the result is displayed at a time. The underlying asset object api is not able to cope with such volume. For using asset objects in statistics gadget, please try to reduce the results returned from your filter.

              7260236ab89d Justin King
              0fb3eca3d13f Alex Pham (Inactive)
              Votes:
              52 Vote for this issue
              Watchers:
              57 Start watching this issue

                Created:
                Updated: