Remove Lookup Issues limit

[Kalliu Gaspar]

Hello to all!

I'm using an automation and I have a problem with the limit of the JQL Lookup Issues.
When I use this formula bellow, it should be returned more than 100 (actually, should be 127). 

parent = "{{issue.parent.key}}" and then creating a variable where it counts the number of issues that epic has > using on a Lookup issues component.

I have found this documentation, but I can't change the limit on the global administration (on my screen only appers some tips and "Allow project administrators to manage project rules.") neither use -1 to remove the limit (actually, I don't know how to do this).

I don't know if everything was understandable...

Thanks!

understandable

[Trudy Claspill]

Hello @Kalliu Gaspar 

It is not possible to change the limit on the maximum number of limits returned by the Lookup Issues action.

You can find that limit and others documented here:

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

If you found documentation indicating that limit can be changed, please provide a link to that so we can contact the author to get it corrected.

If you explain to us the purpose of your rule perhaps we can suggest a work around. Provide screen images that show your entire rule would also be helpful to us.

[Valerie Knapp]

Hi @Kalliu Gaspar , thanks for your post. 

Unfortunately, it's not going to be possible to get around the lookup issues limit https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/ .

What are you trying to achieve?

Best wishes

[Bill Sheboy]

Hi @Kalliu Gaspar 

As several others have described, the Lookup Issues action is limited by the REST API endpoint used to load the matching issues and their fields, up to 100 items.  There is no override to that limit as doing so would impact performance of Jira and rule processing.

Also as others have asked: what problem are you trying to solve?  That is, "why do this?"  Knowing that will help the community offer better suggestions.

Until we know that...

You seem to be asking about how to count issues matching a JQL expression.  When you only need the count, a workaround would be using the Send Web Request action to call the new Search Issues with JQL endpoint, passing the maxResults parameter for up to 5000 issues.  This will only return the issue ID values, but if only the count is needed, that count may be found from the web response.

Kind regards,
Bill

[Jim Knepley - ReleaseTEAM]

Hi @Kalliu Gaspar 

When you say "counts the number of issues that epic has" are you iterating over every returned issue and incrementing a counter? If all you care about is the length of the list of issues, maybe look at {{lookupIssues.size}}, which is just that.

I would see where that value would only ever contain up to the query limit, but it's worth a try.

ref: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-lookup-issues