Defect #35664
Inconsistencies in rendering of subproject data on Issues Reports
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Issues planning | |||
Target version: | - | |||
Resolution: | Affected version: | 4.0.0 |
Description
There are several inconsistencies in rendering of subproject data on Issues Reports after the addition of subprojects-inclusion introduced in #2529 and its extension by #34185. I've put my findings in a table:
Block: | Shows subproject values: | Shows subproject data: |
---|---|---|
Tracker | yes, if with_subprojects=1 | yes, if with_subprojects=1 |
Priority | yes, always ** | yes, if with_subprojects=1 |
Assignee | no | yes, if with_subprojects=1 and only if subproject value is available in current project |
Author | no | yes, if with_subprojects=1 and only if subproject value is available in current project |
Version | yes, always | yes, if with_subprojects=1 |
Subproject * | yes, always * | yes, always * |
Category | no | no |
Legend: | ||
---|---|---|
* | = | only shown when @project.children.any? == true |
** | = | these values are global |
with_subprojects=1 | = | Setting.display_subprojects_issues == 1 |
Related issues
History
#1
Updated by Mischa The Evil 11 months ago
- Related to Feature #2529: Extend Issue Summary to include subprojects added
#2
Updated by Mischa The Evil 11 months ago
- Related to Defect #34185: Trackers of subprojects are not displayed in the Issue summary page added