Registering Webhooks via REST API Returns "Clause Not Supported" Error

Jira Development Jira Cloud
, ,
1

Hi there!

We have a JQL query like this: project = "PROJ" AND "External ID[Short text]" is not EMPTY. The JQL is valid, and we can successfully search Jira issues using this query without any issues. However, when we try to register the webhook, we get the following error:

[ { errors: [ 'Clause External ID[Short text] is unsupported' ] } ]

There is an endpoint in experimental mode that I tested the JQL with, and it confirmed that the JQL is valid. However, for some reason, it’s not working for webhooks.

Is there any documentation that explains the limitations of using webhooks regarding JQL, or is there an endpoint we can use to validate the JQL before registering the webhook?

Thanks in advance!

2

Hello @Vitally

  1. Is ‘External ID[Short text]’ the name of a custom field?
  2. Did the problem go away when you:
  • Removed the square brackets from that field’s name; or
  • Referred to that custom field by its ID not its name in the JQL
3

Hi, thanks for your reply.

Unfortunately, it’s not working with the query: project = "PROJ" AND "External ID" is not EMPTY (without short text). It’s strange because the query is valid—I tested it in Jira and obtained results. For some reason, it’s not working for registering webhooks. It’s also not working when I refer to the ID (included in the Jira search).

Any thoughts?

4

Sorry, but I don’t know why that is happening, as I can’t replicate that problem., I have custom fields with similar names and they work via a webhook if I refer to them by their ID in the JQL.

I suggest you raise a support request ticket with Atlassian.

1 Like