How to use automation to create multiple issues.

[Steve Morales]

Hi Everyone,

We just did a major migration and ended up having hundreds of issues that need to be created for vulnerabilities. Does anyone know how to use automation to create multiple tickets instead of going through each one of them and physically clicking on the "create issue" action? I have tried creating a rule, but I think the rule only applies to new issues coming after the rule was created. Thanks for the help! 

[Benjamin · Accepted solution]

Hi @Steve Morales ,

It is possible to create multiple issues through automation but there's needs to be trigger for each issue to create. The trigger could be schedule job, manual trigger, trigger by an issue update. There's multiple options to choose from.  If you have a list of issues in a CSV, it might be simpler just to import your issues into a project.

-Ben

[Steve Morales]

Thank you for your quick response. The list of issues are actually already in JIRA. We have an integration between our scanning tool and JIRA. So within JIRA, I can see them already but the main problem is that I have to click on each vulnerability individually and click on "create issues" if that makes sense.

[Benjamin]

Not sure what you mean by the need of create issue within a Jira ticket. What does the  create issue button do when selected. Does it create a set of certain issue types?

Based on what you mention,  you may want to run a scheduler to run through a list of jira tickets by on JQL, and set a certain action like create issue.

[Steve Morales]

So we have an integration with Snyk. Within Snyk whenever a vulnerability is detected, the ability to create a ticket will appear within JIRA. We cannot import a CSV file because everything is already viewable withing JIRA. Here is an example of the integration view. This is not our actual company view. I found this in the Snyk website.

[Josephine Turner]

I personally in the past have to delete the security container, set up automation to create a ticket when a vulnerability is found and then I re- add the security container

[Ellen Tushar]

@Josephine Turner , 

Thank you for this solution.  Removing the security container connections and adding them back triggered the automation rule for me.

[Victor Law · Accepted solution]

Hi @Steve Morales

Have you tried creating the Jira issues via CSV import?

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Creating the Jira issues via CSV would make more sense if you have the data ready to be created in bulk.

Thank you.

[Josephine Turner]

@Victor Law If you are creating issues for Vulnerabilities in the security hub with a linked security tool/ app plugin then doing a CSV wouldn't link the vulnerability to the Jira Issue unfortunately. But settting up automation with the Trigger: When a vulnerability is found - Then: Create an issue. And then connecting a security container will not only bulk create issues for all the vulnerabilities found in that security container but allow issues to be created every time a new vulnerability finding is integrated from the security tool into the Jira security hub. 

[Dexter de Vera · Accepted solution]

Hi @Steve Morales ,

Welcome to the Atlassian Community!

You can import csv to create issues in bulk. You may check the link how yo import csv in Jira cloud.

https://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/