All Apps and Add-ons

Add-on for JIRA: How to add multiple fields to initial JQL_Query?

mrfredman
Path Finder

Hi,

I'm attempting to use a standard JQL_Query to filter my JIRA issues down by project and summary before performing any sort of action on them in Splunk, but Splunk only seems to recognize the initial field I enter.

For example, in the following query I get results filtered by Summary but not Project:
|jirarest jqlsearch Summary~"Exercise" AND Project=Support

Do I have the syntax wrong? How can I properly constrain my search from within Splunk?

1 Solution

Flynt
Splunk Employee
Splunk Employee

Great question! The issue is how you are querying. To the JIRA command

|jirarest jqlsearch Summary~"Exercise" AND Project=Support

Is interpreted as Summary~"Exercise" being the totality of arguments passed. In order for the query to work, I would suggest using single quotes for criteria within double quotes for the whole argument. Something like this.

|jirarest jqlsearch "Summary~'Exercise' AND Project='Support' "

View solution in original post

Flynt
Splunk Employee
Splunk Employee

Great question! The issue is how you are querying. To the JIRA command

|jirarest jqlsearch Summary~"Exercise" AND Project=Support

Is interpreted as Summary~"Exercise" being the totality of arguments passed. In order for the query to work, I would suggest using single quotes for criteria within double quotes for the whole argument. Something like this.

|jirarest jqlsearch "Summary~'Exercise' AND Project='Support' "

mrfredman
Path Finder

Worked perfectly. Thanks!

0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...