Feature #35647
Allow the user to properly override Setting.display_subprojects_issues on Issue Reports if a project has subprojects
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues planning | |||
| Target version: | - | |||
| Resolution: |
Description
I'd like to know if there is interest in a feature like this:
2021-07-31_10-49-52.gif - Gif of the POC of the feature. (341 KB)
0001-Dirty-and-untested-POC-for-35647.patch 
- Patch against trunk @ r21131
(7.82 KB)
Related issues
History
#1
Updated by Mischa The Evil over 1 year ago
- Description updated (diff)
#2
Updated by Mischa The Evil over 1 year ago
- Related to Defect #35666: Review incorrect usage of Setting.display_subprojects_issues added
#3
Updated by Mischa The Evil over 1 year ago
- Related to Feature #2529: Extend Issue Summary to include subprojects added
#4
Updated by Mischa The Evil over 1 year ago
- Related to Defect #34185: Trackers of subprojects are not displayed in the Issue summary page added
#5
Updated by Mischa The Evil over 1 year ago
- File 0001-Dirty-and-untested-POC-for-35647.patch added
Here's a dirty and untested patch against current trunk @ r21131 that implements this.
Some notes and warnings on the patch:- used argument is currently
true/false, while in e.g. activity1/0is used - argument handling is sub-optimal at best
style="margin-bottom: 1.4em;"is currently hard-coded in the_options_form.html.erbpartial- sub-project parameter support is implemented for categories block, while the block itself doesn't support rendering of sub-project data (see #35664)
- contains no tests, doesn't modify existing tests and might break existing tests
- contains some duplication