View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update | 
|---|---|---|---|---|---|
| 0023233 | mantisbt | custom fields | public | 2017-08-16 20:51 | 2017-10-08 23:52 | 
| Reporter | cproensa | Assigned To | cproensa | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried | 
| Status | closed | Resolution | fixed | ||
| Product Version | 2.6.0 | ||||
| Target Version | 2.7.0 | Fixed in Version | 2.7.0 | ||
| Summary | 0023233: Issues returned by filter has linked custom fields that are not available as columns | ||||
| Description | Currently, when current project is ALL_PROJECTS, the list of available columns includes all custom fields (linked to any project). 
 Columns selection is currently linked to projects. Ideally they should go i hand with the filter scope. | ||||
| Tags | No tags attached. | ||||
| MantisBT: master fe444f15 2017-08-16 16:10 Committer: dregad Details Diff | Custom field columns include subprojects fields Evaluate subprojects of current project to include readable custom fields in the available columns list. This allows adding a column for a custom field that is linked to a subproject, which is the default behaviour when selecting ALL_PROJECTS. Since columns are related to a project, but the filter by default shows issues from subproject, extending the behaviour for any project/subproject is consistent with the expectation that columns for those custom fields can be used for view-all-bug page Fixes: 0023233 | Affected Issues 0023233 | |
| mod - core/columns_api.php | Diff File | ||
