2

I'm using the Custom Fields plug-in and created a field of type Number. As an example, I set the value of this field to 1, 5, and 10 for 3 different bugs.

When I try to use the Filter UI to search for values "5 or higher" or "5 or lower", I only get the bug where my custom field equals exactly 5.

When I try to do the same thing via search axis, I get even worse results. customxfield:"5" gets me the bug with the field set to 5. customxfield:"..5" and customxfield:"5.." and customxfield:"1..5" (and other variations) get me no results whatsoever.

Is there a correct way for searching custom fields of type Number?

Fog Creek Case FC1957928

flag
See also fogbugz.stackexchange.com/questions/4133/… – Michel de Ruiter Sep 30 2010 at 20:55

1 Answer

1

The range searches on Custom Fields are a known issue, and we'll try to get that into a future version of CustomFields; right now we're not parsing out ranges in the axes.

However, filtering by "or higher" or "or lower" should work, and works properly on my test install. Could you double-check that there aren't other filter constraints that are keeping out the other cases from showing up? If the other cases show up when you set the filter to "customxfield is 10 exactly", but not when you set it to "customxfield is 5 or higher" then we have a bug.

link|flag
It's definitely the case that there are no other filter constraints. I'm simply searching for "all cases where customxfield is [...]" I'm currently running version 7.1.10, so that could be an issue? We are upgrading soon so I will retest once we get a more up-to-date version of Fogbugz running. – rtzong Oct 5 2010 at 19:02
I'm running version 7.3.5 and am still seeing this bug. What version are you running for your test install? We plan on getting 8.0 as soon as we can sort out some kinks we are seeing with getting that running on our servers, but I didn't want to put this on hold for too long if it's just a red herring. – rtzong Oct 7 2010 at 18:54
I'm running 7.3.5 as my test install, so I'm at a loss as to what is going wrong for you; let's get on the phone, and I'll bet we can sort this out quickly; could you call us at 866-364-2733 or email customer-service@fogcreek.com? – Brett Kiefer Oct 8 2010 at 13:31
I had a very nice phone call with Rich and he said he replicated my problem and would file a bug to get it fixed. Thanks. – rtzong Oct 12 2010 at 18:33
1 
Rich got back to me. This particular issue is fixed in the latest version of the Custom Fields plug-in (v1.1.5.0). You need to have FogBugz 8 installed to use this plug-in. – rtzong Oct 13 2010 at 21:35
show 1 more comment

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.