View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0021080||mantisbt||custom fields||public||2016-06-10 03:25||2016-06-12 00:46|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Status||closed||Resolution||no change required|
|Summary||0021080: Filtering on simple custom field of type string does not work|
I've added the "Customer" field to my project in order to track bugs by customer who reported it (it serves as a reminder of whom to reach out once the bug is fixed). I've read about issues where filtering would not work for multiselection list custom fields; but in my case it is a simple string field so I don't have to keep the list updated once a customer arises or gets discontinued. See screenshot ("Cliente" is Italian for "Customer").
I've been experiencing this ever since I added the custom "tested" state system-wide following the steps described here: https://www.mantisbt.org/manual/admin.customize.status.html
|Tags||No tags attached.|
This implies that it was working before - is it really the case ?
I don't have time to check in depth at the moment, but that would be surprising, as if I'm not mistaken the text search only operates on MantisBT "standard" text fields (i.e. Description, Steps to reproduce, Additional information and bug notes)
To filter based on your custom field (regardless of its type), you need to use the specific filter field that should be present somewhere in the form above the "Apply Filter" button.
I'm quite positive it used to work.
And here is the hard evidence that it cannot possibly have, unless you have customized the source code.
As far as I can tell, the system works as designed, so I will close this issue as "No change required". If you feel that the text search should cover all text fields, feel free to reopen the issue; it will then be recategorized as a feature request, but I don't think it will be very high on the priority list unless you are willing to contribute a patch.
Also note that you can perform 'OR' filters by selecting 'Any Condition' in the 'Match Type' form field.
Thanks atrol, fixed by following your link to bug 0007183 and applying customization as suggested by note https://www.mantisbt.org/bugs/view.php?id=7183#c33413
Dregad, not sure if there were prior customizations to source code, but it's possible because colleagues claim it used to work, so one of the steps I followed to add a custom bug state (as pointed out in the additional info) must have reverted such customizations and restored Mantis' default behavoir.
|2016-06-10 03:25||axedre||New Issue|
|2016-06-10 03:25||axedre||File Added: mantis 003.png|
|2016-06-10 04:38||dregad||Status||new => feedback|
|2016-06-10 04:38||dregad||Note Added: 0053299|
|2016-06-10 05:38||axedre||Note Added: 0053301|
|2016-06-10 05:38||axedre||Status||feedback => new|
|2016-06-10 06:50||dregad||Assigned To||=> dregad|
|2016-06-10 06:50||dregad||Status||new => resolved|
|2016-06-10 06:50||dregad||Resolution||open => no change required|
|2016-06-10 06:50||dregad||Note Added: 0053302|
|2016-06-10 08:20||atrol||Note Added: 0053303|
|2016-06-10 09:07||axedre||Note Added: 0053304|
|2016-06-10 09:15||dregad||Relationship added||related to 0011467|
|2016-06-10 09:15||dregad||Relationship added||related to 0007183|
|2016-06-12 00:46||vboctor||Status||resolved => closed|