Content-Type: multipart/alternative; boundary="1778881473-2066066150-1400590493=:41462" --1778881473-2066066150-1400590493=:41462 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I will start over :-).=0A=0ABefore converting, when running 1.1.7 the field= was set up as a multi-selection list.=C2=A0 We really never needed it that= way and nobody who was still here knew why it was - so we decided to chang= e it after I upgraded.=0A=0ASo I upgraded from 1.1.7 to 1.2.17 and did the = checks etc.=C2=A0 Then I changed the type of field to an enumeration and le= ft the same settings for all the other entries for the field.=C2=A0 so basi= cally 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.= =C2=A0=C2=A0=C2=A0 (see attached for current field configuration).=0A=0AWhe= n you filter on an individual tester e.g. km or jsmith, it always comes bac= k empty.=C2=A0=C2=A0 If you filter on a non specific value like the blank/n= o-entry or [any] it works.=0A=0ASo I looked into the DB and realized that t= he value jsmith was being saved as "|jsmith|".=C2=A0=C2=A0 so now jsmith do= esn't match I guess.=C2=A0=C2=A0 Basically I think I need to strip off all = the pipes from the 3 fields I updated from multi-selection lists to enumera= tions.=0A=0AHope this makes more sense.=C2=A0 I really just wanted to make = sure I don't damage anything in doing this.=C2=A0 For now they are back to = multi-selection lists.=0A=0AThank you=0AKM=0A=0A=0A =0A=0A_________________= _______________=0A From: P Richards =0ATo: 'KM' ; 'Help with Mantis' = =0ASent: Monday, May 19, 2014 6:34 PM=0ASubject: RE: [mantisbt-help] Mantis= : custom field not filtering right when=09searching on view issues page=0A = =0A=0A=0AHi KM,=0A=C2=A0=0ACould you send a screentshot of the custom fiel= d configuration so it=E2=80=99s clear what you=E2=80=99ve got set up? (I ca= n then try to reproduce at this end more easily)=0A=C2=A0=0AIn addition, ar= e you saying you think that the behaviour has changed due to updating, or t= hat the configuration of the custom field options has changed?=0A=C2=A0=0AI= n terms of pipes, I might be wrong as I=E2=80=99ve not looked at the code, = but I think there may have been a change to strip trailing |=E2=80=99s=0A= =C2=A0=0APaul=0A=C2=A0=0AFrom:KM [mailto:info4km@yahoo.com] =0ASent: 19 May= 2014 14:14=0ATo: mantis-help=0ASubject: [mantisbt-help] Mantis: custom fie= ld not filtering right when searching on view issues page=0A=C2=A0=0AAll=0A= I have a custom field that was defined for years.=C2=A0 We recently upgrade= d from 1.1.7 to 1.2.17.=C2=A0 We thought everything was fine but it seems i= t is not.=C2=A0 We have a field that we use to designate the tester.=C2=A0 = it is just an enumeration with a list of names and blank.=C2=A0 Nothing fan= cy.=C2=A0=C2=A0 however if we select any name the results are always 0.=C2= =A0 if we choose "[any]" it is fine, and blank is fine.=0A=C2=A0=0AThen I r= ealized that the field used to be a multi-selection list.=C2=A0=C2=A0 After= the conversion to the new mantis version I changed that field to an enumer= ation to allow only one selection.=C2=A0 the database values were originall= y saved with pipes... e.g.=C2=A0 "|myid|".=C2=A0... which I think should be= just "myid" right?=C2=A0 ... in either case.=C2=A0I could see if there wer= e two values then it should be "myid|yourid" or something maybe.=C2=A0 Not = really sure how they are kept.=0A=C2=A0=0ASo for now I have changed 3 of my= fields back to multi-selection lists so the filters work.=C2=A0 Is there s= ome sort of easy way for me to fix this?=C2=A0 I guess I could edit the DB = directly.=C2=A0 =0A=C2=A0=0AAlso - my other question -- should the field ha= ve pipes in it?=C2=A0 what about enumeration fields?=C2=A0 Because the othe= r thing I noticed while doublechecking data after the conversion - some fie= lds had pipes and some did not, even for the same custom defined field.=C2= =A0 =0A=C2=A0=0AThanks=0AKM --1778881473-2066066150-1400590493=:41462 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I will start over :-).

Before converting, when running 1.1.7 the fi= eld was set up as a multi-selection list.  We really never needed it t= hat way and nobody who was still here knew why it was - so we decided to ch= ange 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 settin= gs for all the other entries for the field.  so basically the same men= u 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 indiv= idual 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 work= s.

So I looked in= to 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 m= ulti-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



<= div class=3D"hr" style=3D"margin: 5px 0px; padding: 0px; border: 1px solid = rgb(204, 204, 204); border-image: none; height: 0px; line-height: 0; font-s= ize: 0px;" contenteditable=3D"false" readonly=3D"true">
From: P Richards <paul@mantisforge.org>
To: 'KM' <info4km@yahoo.com>; 'Help with Mantis'= <mantisbt-help@lists.sourceforge.net>
Sent: Monday, May 19, 2014 6:34 PM
Subject: RE: [mantisbt-help] Mantis: c= ustom field not filtering right when=09searching on view issues page

<= style>#yiv0422200732 #yiv0422200732 --=0A =0A _filtered #yiv0422200732 {font-family:Helvetica;p= anose-1:2 11 6 4 2 2 2 2 2 4;}=0A _filtered #yiv0422200732 {panose-1:2 4 5 = 3 5 4 6 3 2 4;}=0A _filtered #yiv0422200732 {font-family:Calibri;panose-1:2= 15 5 2 2 2 4 3 2 4;}=0A#yiv0422200732 =0A#yiv0422200732 p.yiv0422200732Ms= oNormal, #yiv0422200732 li.yiv0422200732MsoNormal, #yiv0422200732 div.yiv04= 22200732MsoNormal=0A=09{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}= =0A#yiv0422200732 a:link, #yiv0422200732 span.yiv0422200732MsoHyperlink=0A= =09{color:#0563C1;text-decoration:underline;}=0A#yiv0422200732 a:visited, #= yiv0422200732 span.yiv0422200732MsoHyperlinkFollowed=0A=09{color:#954F72;te= xt-decoration:underline;}=0A#yiv0422200732 span.yiv0422200732EmailStyle17= =0A=09{color:#1F497D;}=0A#yiv0422200732 .yiv0422200732MsoChpDefault=0A=09{f= ont-size:10.0pt;}=0A _filtered #yiv0422200732 {margin:72.0pt 72.0pt 72.0pt = 72.0pt;}=0A#yiv0422200732 div.yiv0422200732WordSection1=0A=09{}=0A#yiv04222= 00732
Hi KM,
=
&nb= sp;
Could you send a screentshot of the custom field configuration = so it=E2=80=99s clear what you=E2=80=99ve got set up? (I can then try to re= produce at this end more easily)
 
In addition, are y= ou 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=E2=80=99ve not looked at the code, but I thin= k there may have been a change to strip trailing |=E2=80=99s
 = ;
Paul
 
=
From: KM [mailto:info4km@yahoo.com]
Sent: 19 May 20= 14 14:14
To: mantis-help
Subj= ect: [mantisbt-help] Mantis: custom field not filtering right when searching on view issues page
<= /div>
 
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.  i= t is just an enumeration with a list of names and blank.  Nothing fanc= y.   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-sel= ection list.   After the conversion to the new mantis version I c= hanged that field to an enumeration to allow only one selection.  the = database values were originally saved with pipes... e.g.  "|myid|".&nb= sp;... 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-selec= tion 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?&= nbsp; what about enumeration fields?  Because the other thing I notice= d while doublechecking data after the conversion - some fields had pipes an= d some did not, even for the same custom defined field. 
=
 
Thanks
KM


<= /div>
--1778881473-2066066150-1400590493=:41462--