The project status gets assembled at the end of the month. Someone exports issue lists, someone else exports spent time, and out of that comes a spreadsheet that is out of date a week later.
With the Reporting plugin, reports live where the data is. They are current when you open them, because they come straight from issues and time entries.
How it works day to day
- Save a query. You filter the issue list as usual and save the filter. That saved query is the basis for everything else.
- Assemble a dashboard. On the home page and on project overviews you arrange blocks by drag and drop: queries, charts, counter boxes, recently changed issues.
- Pick charts. Distribution by status, tracker or priority, burndown per version, spent time per project. The choice sits on the block, not in a separate view.
- Share. A dashboard can stay private, be shared with others or be set as a system dashboard for everyone.
- Hand it out. Export charts as PNG or PDF and lists as CSV or XLSX when someone needs the figures elsewhere.
What changes
- The report is not built, it is opened.
- Everyone sees the same number, because it comes from the same query.
- Whoever only needs an overview opens the dashboard instead of reading an issue list.
Across project boundaries, the cross project version list helps when several projects work towards the same date.
Which functions the Redmine Reporting plugin brings along and what it costs is described on the product page.