Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
It is possible to search for specific values within a database field using JQL.
Image Removed
JQL Search Example
Given a field like the one configured above, if we wanted to find all the issues that have Nissan cars, we can do that using the JQL function seen belowThe search can be done in two ways: using dbcfExpr JQL function or using issue.property syntax.
The following Advanced Row Field will be used as example for each of the two search options:
Image AddeddbcfExpr JQL function
The dbcfExpr
JQL function is available starting with version 6.1.820.2 and it requires only one argument: a valid JQL string. This JQL string is allowed to refer to any Advanced Database Row Field by its name.
Here is how you can use it to search for issues:
Code Block |
---|
key in dbcfExpr("Country ~ Spain") |
Info |
---|
If a custom field name (or value) contains spaces (or any special character), please enclose it in single quotes. For a field named,
|
If you only want to search for a certain column in the Advanced Database Row Field, you can, using the following syntax:
Code Block |
---|
key in dbcfExpr("Country.code ~ ES") |
When you do not specify a column name the search is done on all columns.
Starting with version 6.2.820.3, to respond to some performance issue that were reported, the dbcfExpr function has an extra parameter that represents the maximum number of results to be shown:
Code Block |
---|
key in dbcfExpr("Country ~ Spain", maxResults) |
maxResults is optional and it needs to be an integer value. If it is missing, the number of results is limited to a default value of 1000.
Info |
---|
It is highly recommended that if you need to apply additional filters to narrow down the search results, to do it inside the dbcfExpr condition, like this:
|
issue.property syntax
The complete syntax to search for issues using this method:
Code Block |
---|
issue.property["dbcf"].customfield_11100_make10300 ~ Nissan |
value |
To see how this function works, lets break it apart:
Prefix - This part of the function is static. This syntax should never change:
Code Block |
---|
issue.property["dbcf"] |
Field and label - The next part of the function is the id of the custom field that is getting searched (Ids will vary across instances. To look up the id of a custom field use the Custom Field Usage tool). Names and aliases do not work in place of the custom field id. After the underscore is the label, this corresponds to the row in the database field.
Code Block |
---|
customfield_ |
10300_ |
name |
Operator and value - It is important to ensure that you are using the proper operator type.
Code Block ~
Spain
String - When searching strings it is recommended to use “~” and “!~” (contains and does not contain) instead of “=” and “!=” to get the
appropriate results.
Numbers and Dates - When searching the normal numerical operators will work, such as “=, !=, <, >
More Examples
Search for
issues missing a value for country:
Code Block
issue.property["dbcf"].customfield_11100_year > 2010
Searching for a car by year and make:
Code Block |
---|
issue.property["dbcf"].customfield_11100_year = 2010 AND issue.property["dbcf"].customfield_11100_make ~ Mazda |
Search for issues missing a value for model:
Code Block |
---|
issue.property["dbcf"].customfield_11100_model is Empty |
Sear for issues with cars made in multiple years:
key in dbcfExpr("Country is empty")
Search for countries having gdp_capita greater than 20000:
Code Block key in dbcfExpr("Country.gdp_capita > 20000")
Searching for a country by name and code:
Code Block key in dbcfExpr("Country.name ~ Spain and Country.code ~ ES")
Table of Contents |
---|
See More
Child pages (Children Display) | ||
---|---|---|
|