|
1
|
I've created a new status called "Inactive". I have some cases with a status of "Active" and some of "Inactive". When I search for:
... I only get the inactive cases - no problem. When I search for:
... I get both active and inactive statuses. Is this due to stemming? Adding wildcards doesn't seem to help.
... works but is a bit ... wordy. Any tips? |
||
|
|
|
1
|
I've also run into this problem. What I do in Foglyn is to search for with all IDs for active statuses ... there is usually one active status per case category (i.e. one for Bug, one for Feature, ...), but thanks to workflow plugin, there may be additional active states, with totally different names. So my advice is to get list of active statuses using listStatuses API XML command and then perform search like shown above. |
||
|
|
|
1
|
It's not exactly stemming, but even simpler substring matches. Most of the axis that correspond neatly to database columns use a basic LIKE '%query%' search. Peter's workaround of using the index is the best answer for exact match. I've never noticed the problem with the status axis, probably because the only queries I give are status:active or status:resolved (in which case I want all possibilities). There's been some thought given to giving more control or tweaking how axis behave, but it's not generally on the short term horizon. Despite users getting caught up from time to time, fixing it would mean a big break from the past. |
||
|
|
