I have three Jira OAuth apps (test, staging, and production) and have been using the REST API search endpoint for an external integration to fetch a specific set of issues. The JQL in the search endpoint looks like this:
<issue property name> = <id>
<issue property name> is a searchable entity property that has been defined by a companion Atlassian Connect app (declared in the descriptor using
In my staging environment, the API request (via OAuth2 3LO) works just fine. I get the expected 200 response. However, in my test environment, I keep getting a 400 response saying
“Field ‘<issue property name>’ does not exist or you do not have permission to view it.”
I spent some time comparing all my configurations (OAuth credentials etc) but couldn’t find any setup differences. I also replicated the request to the /search endpoint with OAuth credentials in Postman for staging and test env with the same result - 400 response in test env and 200 in staging.
Does anyone have an idea why there is a discrepancy between my apps? @sreuter
I did find this paragraph in the guide on OAuth 2 (3LO), however, I am not clear if this is the reason - my searchable entity property is already defined by a connect app.
Apps can store and read the values of entity properties (issue properties and project properties) using the REST API. However, in the current implementation of OAuth 2.0 authorization code grants, apps cannot declare searchable entity properties. This means that if your app uses OAuth 2.0 authorization code grants, it won’t be able to refer to entity properties in JQL queries.