Recently, the "Lookup Issues" action has been added, allowing users to look up issues by JQL and action them using the {{lookupIssues}} smart value, which contains the list of issues matching the JQL query.

After the value is retrieved, the user may need to perform actions on the issues in the list. However, the Branch Rule dropdown does not contain the Lookup Issues result to select from.

If the user wishes to perform actions on these issues, then he/she will need to select the "JQL" condition in the Branch Rule and to do the same JQL query as originally conducted to retrieve the list. This means that the JQL query is executed twice, making the action take longer than necessary.

A potential issue is not all issue properties are made available in the query result (https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues), whereas the user would expect to be able to access all issue properties in a Branch Rule.

If the user were able to directly access the Lookup Issues result in the Branch issue dropdown seamlessly, it would be easier for users to access, and it would be more efficient for the server since the JQL query would only be executed once.