Statistics for Redmine · RedminePRO Docs

Q: No Statistics in the project menu.

The module is off for that project, or the account lacks View statistics.

Q: A project is missing from the all-projects view.

Either its module is off, or the account cannot see it, or Global page projects is set to Only the selected projects and it is not among them.

Q: The figures look stale.

They are cached. Refresh recomputes immediately; lower Cache TTL (seconds) if you need fresher numbers more often, knowing that each recomputation costs more.

Charts that answer the questions a list of issues cannot: are we closing as fast as we open, where is effort actually going, who is carrying what, and which projects are drifting. Four tabs, Lifecycle & flow, Time & effort, Team & workload and Project health, over one project or across everything you can see. Every figure explains how it was calculated, so a number can be argued with rather than merely believed.

What you can do

Availability: Business and above.
Turn it on: Per project: Project → Settings → Modules → tick Statistics.
Permissions: Everything is computed from issues the reader may already see, so the permission controls access to the analysis, never to data behind it.
Settings: The two thresholds turn a percentage into a colour on Project health.
Using it: Open Statistics in a project, or Statistics — all projects from the top menu.

Created against closed, over the chosen period — From a live RedminePRO workspace.

Configure

Settings, permissions, modules and how to use it on RedminePRO Cloud.

Install on your own Redmine

Requirements, install, update and remove, for a self-hosted Redmine 6.

Common questions

No Statistics in the project menu.

The module is off for that project, or the account lacks View statistics.

A project is missing from the all-projects view.

Either its module is off, or the account cannot see it, or Global page projects is set to Only the selected projects and it is not among them.

The figures look stale.

They are cached. Refresh recomputes immediately; lower Cache TTL (seconds) if you need fresher numbers more often, knowing that each recomputation costs more.