Speed performance: Advanced Portal Reports

Speed is an aspect that we have been working on to improve it ever since we launched Advanced Portal Reports. Usually our report loads a lot faster than 10-15 seconds so there should be a reason for the time you need to load. Here are some usual reasons and some ideas you can try to see if the speed will improve:

The network connection

Advanced Portal Reports is now built on Atlassian Forge, which means the app is hosted and managed entirely by Atlassian within their cloud infrastructure. All communication happens securely between your Jira instance and Atlassian’s servers. If you experience delays when loading pages related to Advanced Portal Reports (such as Global Configuration, Get Started, Project Configurations, etc.), it may be due to general connectivity issues between your network and Atlassian Cloud. To rule out network-related causes, you can check your connection to Atlassian Cloud services and ensure there are no disruptions or slowdowns on your end.

The network connection

Advanced Portal Reports is now built on Atlassian Forge, which means the app is hosted and managed entirely by Atlassian within their cloud infrastructure. All communication happens securely between your Jira instance and Atlassian’s servers. If you experience delays when loading pages related to Advanced Portal Reports (such as Global Configuration, Get Started, Project Configurations, etc.), it may be due to general connectivity issues between your network and Atlassian Cloud. To rule out network-related causes, you can check your connection to Atlassian Cloud services and ensure there are no disruptions or slowdowns on your end.

Number of requests visible per page We load our report page by page which means only the first page will be loaded. The default view setting is 20 requests per page but if you have selected 50 or 100 requests this might take more time. Please check and use 20 requests per page if that’s the case.

Number of requests visible per page We load our report page by page which means only the first page will be loaded. The default view setting is 20 requests per page but if you have selected 50 or 100 requests this might take more time. Please check and use 20 requests per page if that’s the case.

Configured columns

As mentioned in the previous topic, we load only the information about the first 20 requests. However, if you have selected many columns we need to extract all custom fields that are configured to be shown. Only once we finish gathering the information, then we show the full report. If you have selected a lot of columns, this might slow down the report a bit.

In addition to that, there are some columns that require more time (for example SLAs). If you have some of these columns, this might slow down the report.

Please try removing all columns expect Summary and Reference and try again. If that speeds up the process considerably you can try adding your columns one by one to see which is the one causing the slow load and contact our Support team to report this.

Configured columns

As mentioned in the previous topic, we load only the information about the first 20 requests. However, if you have selected many columns we need to extract all custom fields that are configured to be shown. Only once we finish gathering the information, then we show the full report. If you have selected a lot of columns, this might slow down the report a bit.

In addition to that, there are some columns that require more time (for example SLAs). If you have some of these columns, this might slow down the report.

Please try removing all columns expect Summary and Reference and try again. If that speeds up the process considerably you can try adding your columns one by one to see which is the one causing the slow load and contact our Support team to report this.