Actions
Defect #35664
open
Inconsistencies in rendering of subproject data on Issues Reports
Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues planning
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
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
Updated by
Actions