Question

We'd like to create custom fields for "First Release Seen In" and "Release Fixed In", so that we can track the lifespan of a bug. For example, a bug might be introduced in v1.5, exist in v1.6, v1.7, v1.8, and v2.0, and then be fixed in v2.1; in this case "First Release Seen In" would be v1.5 and "Release Fixed In" would be v2.1. When a customer encounters a problem running, say, v1.8, we'd search for bugs that match their circumstances with a "First Release Seen In" field of v1.8 or earlier and a "Release Fixed In" of "none" or v2.0 or later.

It looks to me like I can easily set up custom fields for these two pieces of information, but there's no way to do a range search on the field. i.e., I can filter by exact values of each field, but not "=v2.0". Is there a way to do this? If not, consider it a feature request...

Answer 1

FogBugz does seem to surface Lucene's ability to do range searching (using the .. syntax) but (with FB) it does not seem to work with strings.

You can do a search like this (numbers):

case:1..20

but the same type of inclusive search with strings does not work:

assignedto:fred..george

I think the .. syntax was really meant for dates. To see the searching capability of the latest Lucene engine, check out Lucene Range Searches.