at the moment, https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get can only return a maximum of 5 issue properties.
A maximum of 5 issue property keys can be specified.
As issue properties are heavily used by both Marketplace apps and Atlassian products, this number is too limiting.
Is there a way to lift this limit? If not, what is the best way to file this with the relevant teams at Atlassian?
A workaround is use the Issue search endpoint to find a group of issues with particular properties, then use the Get Issue Properties endpoints to iterate through that group to get the additional properties for each issue.
For some background, I want the issue properties for all issues that are returned in the respective invocation(s) of the search endpoint. I’m aware of the get issue properties endpoint, however I would have to call it for every single issue (which in my case, can be thousands), which would not perform at all.
Oh, for sure, I understood your reason for wanting to get all the issue properties from a single call to a single endpoint, but as you’d know, the REST API response limits are there to preserve the distribution of the backend system’s processing equally among all the tenants. One person’s unbounded search for large numbers of issues based on a set of non-indexed custom properties affects every tenant, so that needs to be constrained.
By asking to have the limit increased, the argument gets back into the old loop of… where does Atlassian draw the line? 5 results? 50 results? 500 results? What do they accept as the tolerable affect on system performance. 0.1%, 1%, 10%?
Anyhow, don’t really have a dog in this fight as I don’t store custom properties at the issue level, but I’m in the camp that thinks it’s better to have limits than have consequences.
Maybe raise it as a Feature Request and see if it gains traction?