View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011663 | mantisbt | filters | public | 2010-03-16 06:56 | 2014-02-14 09:16 |
| Reporter | schoppi71 | Assigned To | atrol | ||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Platform | VM-Ware | OS | SuSe Linux Enterprise Server | OS Version | 10 |
| Product Version | 1.2.0 | ||||
| Summary | 0011663: View issue page sorting customized fields failed | ||||
| Description | If I add a customized field and apply it to the 'View Issues Columns' the sort function within the view issue page will fail. I'm using PostgreSQL 8.3.x database. The problem is that within the SQL string an 'AS' is missing: see line 4 in the SQL string: mantis_custom_field_string_table_1.value responsibility --> before responsibility an 'AS' has to be inserted e.g. mantis_custom_field_string_table_1.value AS responsibility | ||||
| Steps To Reproduce | Einter a cusotmized field e.g. responsibility | ||||
| Additional Information | Error message - SQL: | ||||
| Tags | No tags attached. | ||||
|
I installed Version 1.2.1 but the problem isn't solved. |
|
|
same problem here. filter on custom field also crashes with sql-error. |
|
|
This is the problem: mantis_custom_field_string_table_1.value responsibility --> missing AS Winthin version 1.2.4 this is also a problem: mantis_project_table.enabled = 't' instead of mantis_project_table.enabled = 1 Custom-fileds must not contain minus and dots, this will also generate problems within SQL-STring for Postgress |
|
|
Solve the problem: filter_api.php line 922: $t_cf_select = "$t_cf_table_alias.value $c_cf_alias"; |
|
|
the error persists in version 1.2.8 with the bugfix from schoppi only custom fields which are not as type of "list" get sorted. can you confirm this? the sql error with custom fields of type "list" is: |
|
|
This issue is not reproducible with the current version of MantisBT. We recommend that you upgrade to the latest stable version [1]; if after doing so the problem persists, do not hesitate to reopen the issue, with additional relevant information. |
|