View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022325 | mantisbt | filters | public | 2017-02-06 10:07 | 2017-04-01 00:13 |
Reporter | mahindra | Assigned To | cproensa | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 2.1.0 | ||||
Summary | 0022325: Sort by custom field in View issues page - doesn't work - or you will get an error in "filters" | ||||
Description | By definition of a column of a custom field in "my account" - I am not able to sort the entries in filters <pre> | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
mahindra, The provided information is not sufficient to provide any help in resolving the issue. A complete and detailed description is required for the support team to get a clear understanding of the problem. Please explain what you do, what are the results you expect to get and what you actually get. Also provide detailed, step-by-step instructions to reproduce the issue; the additional information listed below may also be useful:
|
|
Thank you for your reply and your patience! It seems that you are right - or this is a problem with the Browser Cache. Because I want to reproduce this at home and put the custom field in the last column - and it works ?? I will get more information - it looks like a browser cache problem |
|
I was able to reproduce this at work - only with IE11. My colleague told me that he deleted the cache, possible he had not closed the browser after that. => You could close the ticket. Thank you!!!! |
|
Thanks for the feedback. |
|
I've figured it out => Database query failed. Error received from database was #1054: Unknown column 'mantis_bug_table.steps_to_reproduce' in 'order clause' for the query: SELECT DISTINCT mantis_bug_table.* FROM mantis_bug_table JOIN mantis_project_table ON mantis_project_table.id = mantis_bug_table.project_id WHERE mantis_project_table.enabled = ? AND ( ( mantis_bug_table.project_id in (1, 12, 20, 25, 11, 21, 10, 15, 14, 16, 9, 22, 6, 13, 7, 8, 18) ) AND ( ( mantis_bug_table.view_state = 10 ) OR ( mantis_bug_table.reporter_id = 5199) )) AND ( ( mantis_bug_table.status in (?, ?, ?, ?, ?, ?) ) ) ORDER BY mantis_bug_table.sticky DESC, mantis_bug_table.steps_to_reproduce DESC, mantis_bug_table.last_updated DESC, mantis_bug_table.date_submitted DESC. Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section. |
|
The error is in the "All Projects" view and you will have to add "tags" and a second field |
|
This is similar to the error we get. |
|
Attention - before reproduce this, open a second tab in the browser with column Settings to be able to "Reset Columns Configuration" in your account! |
|
This is similar to 0021592. However, this error (401), is not the originally posted (202) |
|
How does this relates to permalinks? |
|
Indirect, if it is/was working on his Profile, he is sending the links to others, they have other column definitions, and if this is not compatible, or they sort the results, they have the error. We are using custom fields for hours and weeks so the programmers get the Link with their List and then they sort it |
|
@mahindra Is there other kind of error related to the original report here, or can this be closed? |
|
He also has some Permalinks from 1.3.x out maybe an error handling, if a crashing filter is the result, will be ideal. |
|
Thank you! |
|
No, if there is an error with permalinks it won't be fixed by 0022347 |
|
What about non sortable custom-fields? |
|
I have the same problem, if I click on a custom field header, it does nothing. The link looks like this: |
|
The amps are normal, it's just another mantis bug ;) |
|
Custom fields are always sortable, as far as i know. |
|
I cant reproduce this, still. I have custom fields and the sort fine, from filter, and from column header... |
|
Slowly we get behind it - with Permalinks and the filter errors - this is a mantisbt - 1.3.6 – custom fields are all lower case – this permalink does not work with 2.x.x: mantisbt – 2.1.x – custom fields are upper case like they are defined in the admin dialog: http:// www.YOURDOMAIN.at/mantis/search.php?status[]=10&status[]=20&status[]=30&status[]=40&status[]=50&handler_id=373&sticky=on&sort=custom_Umsetzung%20in%20KW%2Cpriority&dir=ASC%2CDESC&hide_status=-2&match_type=0 <b>1.3.x sort=custom_umsetzung => 2.x.x custom_Umsetzung</b> You could reproduce the error if you define a column in your account settings, were you store everything in lower case. AND If hou have defined a custom-field before in 1.3.x in lower case in “View Issues Columns” and you migrate to mantis 2.x.x, so you will get the error in “view_all_bug_page.php” – that is the cause!!!! |
|
In 1.3.x all permalinks (filters also?) were generally lowercase - so it will be possible to run in problems with mantisbt origin fields. |
|
you remember 2017-02-06 16:07 http://www.mantisbt.org/bugs/file_download.php?file_id=7156&type=bug => custom_umsetzung_in_kw 2.x.x Needs custom_Umsetzung_in_KW |
|
|
|
sorry..., i have custom fields with capital letters, spaces, and symbols, and they work in sorting. Can you provide a more detailed steps to reproduce this issue? Starting from a clean mantis installation |
|
In my case custom field names contain a capital letter (example 'TK'), but To reproduce set a custom field name w/o capitals, then set up the corresponding column in |
|
This is a case sensitive error especially after migration from 1.3.x to 2.0 |
|
As workaround we resetted the columns settings and defined it new case sensitive. After that you could generate new Permalinks 0022325:0055613 and everything is working again. |
|
So it's not an error of 2.0 where could be a case sensitive check in the account settings It's a migration error or a compatibility problem between the 1.x and the 2.x mantis tree |
|
I have tried:
I can't reproduce an error. |
|
Something has stored the different entries earlier. |
|
It's pretty obvious that earlier existed code putting |
|
Than change was made for these: 0020248 0017367 0021713 I'd like to get a reproducible scenario to resolve if there's an error, as a priority. |
|
Sounds good! Thank you! |
|
Is the solution to automatically press the reset columns button during upgrade? |
|
After "Reset Columns Configuration" and doing the patches from 2.1.1, we have no problems any more - also in 2.2.0. It should be enough if the support knows this. |
|
I am resolving this, since the cause seems to be the issue described in 0022555, which has been fixed |
|
Thank you very much. |
|