App loading time and error

Loading time

Can you decrease the report’s loading time?

Yes. The number of work items in the report source, such as a space or filter, directly affects Jira’s API performance, which determines the report’s loading time—not Worklogs Report itself.

• To speed up loading, reduce the number of referenced work items.

• Also, specify which spaces or boards Jira should search. A narrower search scope means fewer work items for Jira to process, resulting in faster results. Atlassian’s documentation offers additional JQL optimization tips.

Can reports display more work items than Jira, and what is the impact?

Yes. Reports can display more work items than a board or the Issue Navigator. However, loading time increases as the work item count grows.

Working with high work item count in Cloud

Atlassian notes that searches have no work item limit, but display limits apply:

• Boards and backlogs show up to 5,000 work items.

• The Issue Navigator shows only the first 1,000 work items.

A report can help you work around certain Jira limits, though it may increase loading time. For example, a board may fail to load if it reaches the maximum work item limit.

In contrast, you can create a report based on the board or its underlying source filter. However, this report may take longer to load compared to one linked to a board that has not reached the maximum limit.

Working with high work item count in Data Center

The display limit for the Issue Navigator can be increased using a documented workaround. A report does not require this workaround, although very large reports may load more slowly.

Similarly to prior example, a report linked to a board or its underlying source filter may take longer to load if the workaround was applied to increase the limit.

Loading error

How can you resolve the “Something went wrong” error while loading Worklogs Report?

This error may appear when the app loads slowly and then fails. Common causes include:

• Expired access token – Reload the page to see if the error no longer appears.

• Firewall restrictions – Your firewall may be blocking the atlassian.net domain. Although .net is a common top-level domain, some customers have recently needed to explicitly allow it.