Multiple users running heavy reports in Tempo like Reports without filters or with years of period; are known to cause impacts in Jira (Slowness or even crashing the whole instance) as a lot of resources needs to be allocated to perform these actions.
We understand that a hard limitation exists: https://tempo-io.atlassian.net/wiki/spaces/KB/pages/2615574566/Managing+Worklog+Limits+for+Reporting+Data+Center
But, this approach might be too confusing or prone to questions for the users.
So we would like to share some ideas that could also help users avoid creating some of these problems and might be a bit more user friendly.
Limit the Report date range
Admin setting to set the maximum range of the Report date picker
ie. less than or equal to 12 months, 6 months, etc.
Disallow empty ‘Filter by' in Report
Admin setting to enable / disable Report generation with empty ‘Filter by’
If the ‘Filter by’ box is empty, users should not be able to create a Report, and the Report should not auto-refresh
ie. Jira issue search has similar feature: ‘Disable empty JQL queries’
Access Control List on the Report menu option
Admin setting to assign Jira groups to control who can access the Report
Tempo Products | Tempo Timesheets, Tempo Planner |
Tempo Platform | On-Premise |