This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
1 Replies Last post: Jan 20, 2010 10:40 AM by Jason Goetz  
Lisa Watts   15 posts since
Dec 15, 2009
Currently Being Moderated

Jan 19, 2010 2:10 PM

Defect in 2.8.1 Search Feature?

We upgraded our production system to 2.8.1 over the weekend (coming from 2.6).  A team member has reported to me today what they believe to be a defect in the search feature.  It would seem that the search had previously performed a "like" search but now seems to require matching on an entire phrase.  Let me give an example to help illustrate this behavior.

 

In our system, our numbering scheme on our requirements is "ELB-REQ-###".  We excecuted a search using a partial ID value ("REQ-141").  In the past, this would have yielded a search result that included the record with ID # "ELB-REQ-141", however the current version yields no matches.  The only way to return a match is to enter the full ID value of "ELB-REQ-141".

 

Is this a defect, or by design?  If by design, our feedback would be that we prefer the previous functionality.  :-)

 

Thanks in advance for your review and response!

 

Lisa

Jason Goetz   5 posts since
Dec 2, 2009
Currently Being Moderated
1. Jan 20, 2010 10:40 AM in response to: Lisa Watts
Re: Defect in 2.8.1 Search Feature?

Hi Lisa,

 

Thanks for your question. This is working as designed. You are right that your example case was working before and is not working now. Here is the reason:

 

Previously we would allow our searches to break up hyphenated words into separate words. So, ELB-REQ-141 becomes ELB, REQ, and 141. Now, we treat hyphens as just another character, so ELB-REQ-141 remains as one word. Because you can't search on word fragments (like with most search engines), a search on REQ-141 would return no results. We changes this due to requests from some other customers.

 

However, there is a way you can do a search like this. Our search engine allows for the use of the '*' and '?' characters as wildcards. So, if you want to search for all ELB-REQ items you could say "ELB-REQ*" in your search and get all the items that start with ELB-REQ. The only catch is that our search engine (Lucene) doesn't allow for a * at the beginning of a search phrase. So, *REQ-141 would cause an error, but E*-141 would give you the result you're looking for.

 

I hope that clears this up. Let me know if you have any other questions.

 

By the way, Jama has moved to a new system for support questions. You can send an email to support@jamasoftware.com or log a question directly on the web at support.jamasoftware.com. We continue to monitor Jama Backstage, but it's somewhat infrequently, so we can ensure a much quicker turnaround on questions if they are in the new system.

 

Thanks,

 

Jason Goetz

Jama Software

More Like This

  • Retrieving data ...