Searching with Wildcards

Hi Marcel,

We do support wildcards and other search operators. I typically use the search box in the bar below the main navigation, but wildcards appear to work when constructing filters or doing an "Advanced Search," too.

• Use <em></em>? to perform a single character wildcard search. This would return results containing failure or fialure

f??lure

• Use * to perform a multiple character wildcard search. This would return results containing with, without, within and the term tests
       
with* tests

You can also use quotes to search for phrases, parentheses for grouping, and AND, OR, and NOT operators (they must be all caps, like that) to get more specificity. In the search box, you can also search in specific fields by prepending the name of the field and : to the search terms:

(America OR Europe) description:"needs input" AND NOT product_status:done

If you have field whose label is more than one word, use an underscore instead of a space to reference the field, like with Product Status above.

I hope this helps your users. There is some additional information on searching in the Help file, but this covers a majority of what's there.

Victor,



We have limited support for these on the endpoint. I spoke with one of our REST engineers and he said you can use double-quotes to include the boolean operators and wildcards. At this time, you cannot include phrases inside the double-quoted string, however (by escaping the quotes, for example).

This would find abstractitems with "apple" or "applesauce" in their text:

"apple*"

This would return the same abstractitem results as above, but not any that have juice or juicy in their text:

"apple* NOT juic?"

Hi Victor,

Your syntax was fine (and actually enlightening. I didn't consider trying a query with quotes within quotes. I does work, just not with wildcards.) At this time, we don't support the combination of quoted phrases + wildcards inside double-quoted search strings. It's not exactly the same query as a quoted phrase, but you might get similar (enough) results with something like:

"name:vid* AND name:support"

I'm filing a request to bring the api's query syntax into parity with the application's for phrases like this.

-t

------------------------------
Todd Lemoine
Senior Front-end Engineer
Jama Software
Portland OR
------------------------------
-------------------------------------------
Original Message:
Sent: 03-01-2018 17:55
From: Victor LastName
Subject: Searching with Wildcards

Hi Todd,

Thanks so much for your help.

In my tests, the wildcards do not seem to be working for the /abstractitems endpoint when I use them in the "contains" field in swagger.

For example, when I enter the following into the contains field:  "name:"video support""

I am getting results back with items having the words "video support" somewhere within the Name field.

However, when I experimented with the "*" and the "?" like in the following screenshots, I did not get any results back:


Is my syntax correct?

Thanks,

------------------------------
victor
------------------------------

Original Message:
Sent: 02-26-2018 13:52
From: Todd Lemoine
Subject: Searching with Wildcards

Victor,



We have limited support for these on the endpoint. I spoke with one of our REST engineers and he said you can use double-quotes to include the boolean operators and wildcards. At this time, you cannot include phrases inside the double-quoted string, however (by escaping the quotes, for example).

This would find abstractitems with "apple" or "applesauce" in their text:

"apple*"

This would return the same abstractitem results as above, but not any that have juice or juicy in their text:

"apple* NOT juic?"

------------------------------
Todd Lemoine
Senior Front-end Engineer
Jama Software
Portland OR

Original Message:
Sent: 02-25-2018 12:37
From: Victor LastName
Subject: Searching with Wildcards

Hi Todd,

This is the kind of information I have been searching for but cannot find in any Jama help documentation at all.

Can these wildcards, quotes, AND OR NOT operators be used in a similar manner with the /abstractitems REST endpoint Contains field parameter to further refine the search results?

Thanks,



------------------------------
victor

Original Message:
Sent: 02-23-2018 16:17
From: Todd Lemoine
Subject: Searching with Wildcards

Hi Marcel,

We do support wildcards and other search operators. I typically use the search box in the bar below the main navigation, but wildcards appear to work when constructing filters or doing an "Advanced Search," too.

• Use <em></em>? to perform a single character wildcard search. This would return results containing failure or fialure

f??lure

• Use * to perform a multiple character wildcard search. This would return results containing with, without, within and the term tests

with* tests

You can also use quotes to search for phrases, parentheses for grouping, and AND, OR, and NOT operators (they must be all caps, like that) to get more specificity. In the search box, you can also search in specific fields by prepending the name of the field and : to the search terms:

(America OR Europe) description:"needs input" AND NOT product_status:done

If you have field whose label is more than one word, use an underscore instead of a space to reference the field, like with Product Status above.

I hope this helps your users. There is some additional information on searching in the Help file, but this covers a majority of what's there.

------------------------------
Todd Lemoine
Senior Front-end Engineer
Jama Software
Portland OR

Original Message:
Sent: 02-21-2018 09:51
From: Marcel Bachus
Subject: Searching with Wildcards

Many of our users have asked me if it was possible to search/filter with Wildcards, as they find that it is not always possible to get to many records with CONTAINS.

------------------------------
Marcel Bachus
Innolux Europe B.V
------------------------------