Automation to create child tickets for each found asset

[Kevin Granger]

I have an integration with a VM service, and want to automate child ticket creation on ticket arrival. This is what the description looks like when the ticket comes in;

Apply patch Upgrade to 7-Zip version 18.05 to fix vulnerabilities: [7-zip-cve-2016-2334] on assets [, delt.assess.int, delt24z6.assess.int, delt2lhgk13.assess.int, deltg4, deltb3, LEltb2, deltb1]

Any suggestions on how each of the above mentioned assets could be turned into separate child tickets, as well as when a comment with more assets comes in from the same software, doing the same to make additional child tickets referencing the asset names as well? The comments comes in looking like this 

Detected new assets and/or vulns at (2023-02-16T01:40:38+0000): Apply patch Upgrade Azul Zulu to the latest version to fix vulnerabilities: [No new types of vulns detected] on assets [delt5]

I really appreciate any help. I can't seem to get this to work in any way shape or form.

[James Navin · Accepted solution]

Hi Kevin,

The rule will be a little complex, but you might be able to approach it as follows:

• Trigger on issue create (with appropriate filtering to identify the issues you care about)
• Use the Create variable action to create a new smart value that holds the parsed list of assets you want to create issues for. You would get this parsed list by doing smart value manipulation of the issue.description field - probably some combination of "substring" and "split" operations - see https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/
• Once you have the smart value holding the list of values you would branch over it using the Advanced branching 
• Within the branch you would use the Create issue action to create the new child issue.

The trickiest bit will be getting the parsing of the issue description to work reliably. If you have control over the shape of that description you might be able to make it simpler to parse, or even better put the assets in a custom field on the issue and then write a rule that fetches them from the custom field.

Hope that helps,

James

[Kevin Granger]

I did eventually figure it out. You were right and the solution relied solely on that smart value.