We implemented the check issues against jql api endpoint in our application which is available here: https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-search/#api-rest-api-2-jql-match-post, and when testing it's functionality with our components we noticed that on different environments we are getting different responses. Namely, on one environment when trying to get back issues for 100 ids it works fine, but on another environment when trying to do the same thing we are getting an error: {"errorMessages":["Too many issue ids: 100, maximum number: 50"],"errors":{}} What's really strange is that the documentation of the endpoint doesn't specify a certain maximum number for the ids we are trying to match, and the response doesn't provide a parseable error message. Is there a any reliable way of checking how many issue ids will this endpoint allow us to send at a time?
@Connect ,
As the documentation does not provide a clear maximum number it might be best to raise the issue with support (https://support.atlassian.com/contact)
As they manage the endpoint they should be able to get you a definitive answer.
The difference in responses are they perhaps on a production and a sandbox environment?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.