Thanks for the help. I ended up modifying all of the data to remove the pipes
from the fields that I wanted to change from multi-selection lists to
enumerations. Then I converted the fields to the enumerations.
Everything is working fine now.
I am not sure if this is a bug in mantis. Basically, if custom field is
converted from a multi-selection list to another type of field should more data
modifications be done? Or maybe the searching needs modifications?
Thanks
KM
________________________________
From: KM <info...@yahoo.com>
To: Help with Mantis <mantisbt-help@lists.sourceforge.net>
Sent: Wednesday, May 21, 2014 4:56 PM
Subject: Re: [mantisbt-help] Mantis: custom field not filtering right when
searching on view issues page
Sorry - I just want to be sure what you mean by your statement:
"In terms of |moo| - that should be fine in the DB I think." .
Fine in what way? I do not get errors - when viewing issues, but if I searched
for moo it will come back with no issues because it only has "|moo|" in the DB
(if I change it to an enumeration after being a multi-selection list).
BTW - we also have a few scripts that use the web services to update records to
sync them with another ticket system and I am getting similar errors there for
another update in which I had to change the way the custom field is set up.
The old data has pipes and it doesn't like it. Error is "Invalid custom field
value".
I hope I am making sense. I do still think that I need to strip the pipes from
all the custom field values that I have changed types for.
Also - I guess the key for your testing is to set up a multi-selection list and
enter a few issues. then edit the DB to make sure there are pipes in the
values if they don't get saved that way, then try the tests. You will see what
I mean. like below when I query the DB for distinct values in the Tester
custom field I get the following:
select distinct value from mantis_custom_field_string_table WHERE field_id =
'4';
+----------------+
|
value |
+----------------+
| |
| |jdoe| |
| |gsmith| |
| |QA| |
| |NotQA| |
| |km| |
+----------------+
Thank you for looking at this. I am pretty sure nothing will be destroyed by
my removing the pipes.
KM
From: P Richards <p...@mantisforge.org>
To: 'KM' <info...@yahoo.com>; 'Help with Mantis'
<mantisbt-help@lists.sourceforge.net>
Sent: Wednesday, May 21, 2014 3:26 PM
Subject: Re: [mantisbt-help] Mantis: custom field not filtering right when
searching on view issues page
In terms of |moo| - that should be fine in the DB I think.
My initial stab at copying this setup in against 1.3-master seems to show it
working fine. I’ll have to install 1.2.17 to check out whether it breaks in
that version.
Paul
From:KM [mailto:info...@yahoo.com]
Sent: 20 May 2014 13:55
To: P Richards; 'Help with Mantis'
Subject: Re: [mantisbt-help] Mantis: custom field not filtering right when
searching on view issues page
I will start over :-).
Before converting, when running 1.1.7 the field was set up as a multi-selection
list. We really never needed it that way and nobody who was still here knew
why it was - so we decided to change it after I upgraded.
So I upgraded from 1.1.7 to 1.2.17 and did the checks etc. Then I changed the
type of field to an enumeration and left the same settings for all the other
entries for the field. so basically the same menu entries are valid, just want
to use a normal drop-down enumeration where only one entry is allowed and not a
multi-selection list. (see attached for current field configuration).
When you filter on an individual tester e.g. km or jsmith, it always comes back
empty. If you filter on a non specific value like the blank/no-entry or [any]
it works.
So I looked into the DB and realized that the value jsmith was being saved as
"|jsmith|". so now jsmith doesn't match I guess. Basically I think I need
to strip off all the pipes from the 3 fields I updated from multi-selection
lists to enumerations.
Hope this makes more sense. I really just wanted to make sure I don't damage
anything in doing this. For now they are back to multi-selection lists.
Thank you
KM
From:P Richards <p...@mantisforge.org>
To: 'KM' <info...@yahoo.com>; 'Help with Mantis'
<mantisbt-help@lists.sourceforge.net>
Sent: Monday, May 19, 2014 6:34 PM
Subject: RE: [mantisbt-help] Mantis: custom field not filtering right when
searching on view issues page
Hi KM,
Could you send a screentshot of the custom field configuration so it’s clear
what you’ve got set up? (I can then try to reproduce at this end more easily)
In addition, are you saying you think that the behaviour has changed due to
updating, or that the configuration of the custom field options has changed?
In terms of pipes, I might be wrong as I’ve not looked at the code, but I think
there may have been a change to strip trailing |’s
Paul
From:KM [mailto:info...@yahoo.com]
Sent: 19 May 2014 14:14
To: mantis-help
Subject: [mantisbt-help] Mantis: custom field not filtering right when
searching on view issues page
All
I have a custom field that was defined for years. We recently upgraded from
1.1.7 to 1.2.17. We thought everything was fine but it seems it is not. We
have a field that we use to designate the tester. it is just an enumeration
with a list of names and blank. Nothing fancy. however if we select any name
the results are always 0. if we choose "[any]" it is fine, and blank is fine.
Then I realized that the field used to be a multi-selection list. After the
conversion to the new mantis version I changed that field to an enumeration to
allow only one selection. the database values were originally saved with
pipes... e.g. "|myid|". ... which I think should be just "myid" right? ... in
either case. I could see if there were two values then it should be
"myid|yourid" or something maybe. Not really sure how they are kept.
So for now I have changed 3 of my fields back to multi-selection lists so the
filters work. Is there some sort of easy way for me to fix this? I guess I
could edit the DB directly.
Also - my other question -- should the field have pipes in it? what about
enumeration fields? Because the other thing I noticed while doublechecking
data after the conversion - some fields had pipes and some did not, even for
the same custom defined field.
Thanks
KM
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
