Extend Issue Summary Report to optionally include sub projects
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.
#2 Updated by Ewan Makepeace over 9 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 about 9 years ago
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 :)
#9 Updated by Terence Mill over 5 years ago
I am wondering because in favour of the new admin issue setting "Display subprojects issues on main project" one could imagine all views (not only issues, gantt and calendar) will show defaukt all (subprojects issues) in any parent view if this switch is true.
However it shall be possible to be able to apply filters (with or without subprojects -selction) in every view.
#16 Updated by Mizuki ISHIKAWA 7 days ago
Redmine has the setting "Display subprojects issues on main projects by default".
Whether subproject issues are displayed on the issues/index is determined by the setting.
I think that the summary report should be counted in the same way as issues/index.
I attached a patch for that.
- Target version changed from Candidate for next major release to 4.1.0
The patch works fine for me. Issues in subprojects are counted if the value of
true. I think the behavior is consistent with the issues list.
Setting the target version to 4.1.0.