Is it possible to automatically create multiple Jira issues using the JQL condition?

[Radl Glück]

Hello, 

I want to automate the creation of Jira issues. If CR issues will appear in a certain JQL search, other issues for testing should be created in a different project. I want that every day it will be checked if new CRs issues are here, which do not have test issues linked to them. 

I made my first draft for the automation rule and I have questions for that. 

1. I need different criteria for different JQLs --> so I use an If/Else block. If one JQL search finds multiple issues, does the 'Create a new' action create only one issue or one issue for each found? This is important to know because more than 50 tickets will certainly need to be created.
2. Do the smart-values issue.key and issue.summary match to transfer them from the trigger issue to the new one?
3. If I want to link the tickets together, does the selected field 'Linked Issues' match? Because how I build my JQL search that if the test issue is created and linked with the CR issue the JQL search for the CR issues won't find it anymore --> so it won't happen that infinte issues will be created in a loop.

Screenshots are attached for better understanding. 

Thank you for your help.

[Trudy Claspill]

Hello @Radl Glück 

1. When you use a Scheduled trigger to get a list of issues using JQL, the remaining steps in the rule will be applied to each issue found by that JQL.

2. If you want to copy data from the issue found in the trigger's JQL to the issues you are creating, I recommend you use {{triggerIssue}} instead of {{issue}}.

3. This is more difficult to answer without having more details about the JQL statements you are using and where you are creating the issues. Can you substitute in place holders like "Project A" and "Project B" where you have redacted data?

I am not 100% sure but I think that the JQL in the trigger runs once at the beginning to get the initial list of issues. If you create more issues during the rule that would match the JQL in the trigger, that should not change the initial results of the trigger JQL. If the trigger JQL returned 5 issues, then the actions in your rule should be executed for only those 5 issues.

[Dick]

Hi @Radl Glück 

Regarding your questions:
ad 1: it will execute for each of the found issues, each triggering one creation of a ticket 

ad 2: you can always refer to these fields of the initial issue as triggerissue.key and triggerissue.summary

ad 3: The linked issue field will be filled with the key of the created issue in the alternate project (abc-123). 

When I come to think of the goal of your automation, and what it replaces, I cannot escape the thought that it might be better to build the transfer of work to team B into the workflow of the first team (A) by providing a status (with transfer) to it.

This way, it is possible for both teams to work more tightly together, increasing throughput and quality by mutual understanding and acknowledgement of the preceding and following work respectively. These are in my honest opinion the most valuable benefits that always should be taken into consideration before creating an automation.

Kind regards,

Dick