Any option to override JQL result in "Scheduled" automation and clone result of some new JQL ?

[Arundev N B]

Hi
My requirement

1. Need to run a scheduled automation rule but it is must that we need a jql to trigger it.

2. But on some condition I need to clone some new issue which is not in above jql result. This is not happening now even after using LookUpIssues and various conditions too.. 

3. Clone an issue other than the result of 1st jql . use a new jql and clone result of that output. 

Possible ? 

[Andy Heinzer]

Hi Arundev,

If I understand your request here, you want to run an automation rule in Jira that is using a Scheduled trigger.  When you use that trigger there is an option to use JQL to search issues within Jira. 

Any actions that happen there are bound to the subset of those JQL results.  There is no way to then expand the JQL results and execute some set of actions on issues not within those results.  The only exception I can think of this is the branch rules.  These can let you perform actions upon related issues to the JQL results, but these have to have existing issue links, epic link, or be a subtask of a parent issue.

There is also a project limiting factor here when using project automation vs using a global automation rule.  Any automation rules created within the Project settings > Automation are also limiting those JQL results to that specific project.  Global automation rules don't have this restriction, but they do have to deal with execution limits as these tend to have a greater potential impact on system performance.

I am interested to learn more about your need here.  What information within the Jira issues are you looking to discover in order to determine whether or not to clone them?  I don't understand how it is that you are running this first JQL query, and then determining that there are other issues that need to be cloned as a result of that first query.

Andy