Why does the Ultimate Controller take so long to load?

Owned by Ultimate Dashboard for Jira
Apr 27, 2023
2 min read

The Ultimate Controller gadget actually needs to know quite a wide breadth of information about your organization’s filters, sprints and projects.

 

The process of asking Jira’s REST API for all of this information is not always straight forward, for example to determine a list of all possible statuses to present in the controller’s user interface, the controller gadget must check each project for the available statuses for that specific project and then add those to the overall list of statuses users can pick from.

 

all Ultimate Dashboard for Jira gadgets are entirely “client side” and do not communicate with any of our web services, they all use Jira’s REST and JavaScript APIs directly and as such all the stuff that would have happened on the Ultimate Dashboard for Jira server-side happens instead within the browser viewing the dashboard gadgets - doing this protects your data with the highest level of security we can provide while still providing ultimately useful dashboard gadgets

 

Given that all of this is happening in the user’s browser session (client-side), that means the performance of the gadget is dependent upon a number of things which are entirely beyond Ultimate Dashboard for Jira’s control…

  • how many projects and issues there are within the organization (increases the amount of work needed to be done)

  • how fast the network is between the browser and Jira’s API servers (increases the amount of time it takes to do increments of the work needed to be done)

    • for example, using Ultimate Dashboard for Jira on a 3G hot-spot is going to load slowly

  • how much memory there is available to the browser (limits how fast the browser can do the work)