Feature #2529
Extend Issue Summary Report to optionally include sub projects
| Status: | New | Start date: | 2009-01-19 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Issues | |||
| Target version: | Candidate for next major release | |||
| Resolution: |
Description
When I view issues for a parent project I am shown issues from the parent and all sub projects mixed together. When I click the summary link on the same page the summary I am shown is for the parent project alone. This behaviour is completely unexpected and not at all obvious at first glance.
It would be extremely useful to have a summary display of ALL the issues in the parent and all subprojects rather than the parent project alone.
Related issues
History
#1 Updated by Ewan Makepeace over 3 years ago
Just remembered - to confuse matters further, if you click any of the hyperlinks on the summary page the filtered issues list shown IS for parent and all subprojects, so the issue count does not match the value on the summary.
#2 Updated by Ewan Makepeace about 3 years ago
Extension: I realise that what I really want is a Summary report based on the issues shown on ANY issue view.
Explanation: The issue summary for a mature project quickly becomes rather irrelevant - it shows 100's of long closed issues and many of the open issues are part of that huge and growing population of 'unscheduled' items (stuff requested by idiots that we are too polite to just delete in many cases :-) Having a summary of all issues becomes less and less practical.
What would be extremely useful would be the Summary format extended to any arbitrary collection of issues:
1) Select a custom saved query or build a new one.
2) Pick Summary from the right side menu - should always be available.
It should summarise just the issues that are returned by the query. From there of course I can drill down by Assigned To, Category or Target Version (for example) which makes the query a bit more complex... but I think not impossible?
#3 Updated by Ben Blier almost 3 years ago
+1
I just noticed this going through and testing the STI changes after patch #3007. The summary page does its calculations ONLY on the project you are viewing and NOT on any of its subprojects. I'm still getting a feel for the whole Ruby coding language and the Redmine project, but this seems like a extremely simple patch :)
#4 Updated by Etienne Massip about 1 year ago
- Category set to Issues
- Target version set to Candidate for next major release
#5 Updated by Daniel Albuschat 3 months ago
+1
This is really necessary for me to make use of the summary at all ;/