Invalid JQL for Custom Field in Slack Integration

[Elliott Peterson]

I've tested the following JQL successfully in queues, and it works as expected. However, when trying to implement the same logic in a different context, I'm encountering an error that I can't seem to resolve. "Request Type" is a custom field to help us differentiate between different service requests. I've tried multiple variations of the query without success.

Has anyone else run into a similar issue, or is there something I might be overlooking?

As a temporary workaround, I’m using an automation rule to trigger a message via legacy webhooks. Unfortunately, these lack support for newer Slack features and may eventually be deprecated or disabled, which is far from ideal.

Any insights or suggestions would be greatly appreciated!

[Ankit Srivastava]

Hi @Elliott Peterson 

Welcome to the Atlassian Community!

Is the same JQL is working of Jira?
If  not then please use the "Custom_field_id" instead of name "Request Type" and also make project specified.

For eg: Project = ABC and customfield_10010 = "Licensing and billing questions"

And also that custom field is configured in your field/screen scheme.

Hope this will help.

Thanks,
Ankit Srivastava

[Elliott Peterson]

Yes the same JQL is working in Jira. It's bizarre. I have also tried the method you mentioned above. 

examples of it working:

examples of it not working in slack integration with your suggested method:

[Christopher Yen]

Hi @Elliott Peterson 

Welcome to the community!

Hopefully those Slack webhooks do not get deprecated because I have a lot of notifications utilizing those! 

It is odd that if your JQL is working in queues it's normal to assume it should be valid here, can you try switching to basic query to see if Request type is available? I've only used the Slack integration in Software projects and have always used either webhooks or operation alerts for JSM, it's possible the integration doesn't support using request type as it's JSM specific and the Jira Cloud Slack Integration I believe is geared around Jira (software / work management) 

If you're not already utilizing the Jira Assist Agent channel this can be used for a specific request type, the only limitation is that there can only be 1 agent channel per project (Suggestion to allow more can be voted on here)

[Elliott Peterson]

Thanks for the assist agent channel idea, but I'm doing this for several different "Request Type", which is a custom field and not in the basic query.

Also, you can see the worry I have concerning webhooks if you follow the documentation provided by the UI to create the notifications: https://www.slack.com/marketplace/new/A0F7XDUAZ-incoming-webhooks?app=A0F7XDUAZ-incoming-webhooks