Third party applications can extend Automation for Jira by adding custom rule components, such as triggers, conditions, and actions. These custom rule components use ComponentInputs from automation-thirdparty-api maven artifact, which facilitates obtaining the necessary inputs for executing a component based on the outputs of previous rule components.

The method (ComponentInputs.getIssues) for retrieving the list of issues does not preserve the order specified by prior rule components. For instance, if a rule has a scheduled trigger with a JQL that includes an ordering criteria, the list of issues provided to a subsequent third party action does not reflect that order.

Maintaining the order of issues as defined by the trigger or previous rule component would allow third-party components to process the issues in the same sequence.