Edit a report | Colined Help Center

This article explains how to edit an existing report.

How can you edit the report?

If you are the report owner or a report admin, you can edit the report in the following ways:

To update the Sources, Summary, or Breakdown sections—for example, by changing the Project or Filter, Users, or Date Range—make your changes directly in the report. They are saved automatically.
To change the report Name, Description, Admins, or sharing settings, click the down arrow (⌄) next to Save, then select Configure from the Header section.
After making your changes on the Configure page, click Save.
To apply the changes, click Save in the Header section.

To learn more about these fields, see the related article.

If you are not a report owner or report admin, you can save your changes only by creating a copy of the report.

Click Save As in the header to create a copy, then make your changes to the new report.
Alternatively, on the Manage Pivot Reports page, select Copy from the actions (•••) menu.

Access to all users’ worklogs is also controlled at the app level, as explained in a related article.

FAQ

Why and how should you edit the name and description?

Over time, a report's audience and focus may shift, even if its configurations stay the same. Updating the report's name and description to align with its current scope helps users understand its purpose before exploring its tabs.

Troubleshooting

Can reports be used to display more deliverables than possible in Jira?

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

Working with high issue count in Cloud

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

Boards and backlogs show up to 5,000 issues.
The Issue Navigator shows only the first 1,000 issues.

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 issue 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 issue 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.

Can you decrease the report’s loading time?

Yes. The number of issues in the report source, such as a project 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 issues.
Also, specify which projects or boards Jira should search. A narrower search scope means fewer issues for Jira to process, resulting in faster results. Atlassian’s documentation offers additional JQL optimization tips.

In Jira Data Center, alerts help identify slow and complex JQL queries, including those with many custom fields. Atlassian provides detailed thresholds for these alerts in a separate article.

If you have questions or need assistance, contact our support team via email or service desk. Our team is available Monday through Friday (9:00 AM to 7:00 PM GMT+7) to help with technical challenges or discuss improvements.