Hi everyone,
I’m setting up a Jira Automation rule in my EST jira project to re-route newly created security issues into the appropriate team backlogs. Our security tool creates tickets in EST with a description block like:
Category: Cloud Security Issue
Application Name: *AWS-124289522
Severity: High
I’d like to automatically route security issues into team-specific Jira projects based on the “Application Name” prefix. For example, any issue whose description includes:Application Name: AWS-...
should be cloned into the DevOps project backlog. We’ll use the application name to determine the correct team, and we already maintain a registry mapping each application to its Jira project. Could you recommend the best way to automate this process via Jira automation from scratch?
I've uploaded a screenshot of what I've made so far.
you'll need a mapping between projects and keywords. This should work both with assets or a lookup table in your rule.
Extract the prefix with a match.
Add the projectId's in either table and use a smart value for project when creating the new work item.
Best,
Bob
Hi @Bob Dalm
I’m new to this and could use your help troubleshooting. Here’s the automation rule I’ve set up:
Trigger: Manually triggered
Action: Create lookup table
Key: AWS = VST (where “VST” is the project I want to clone the issue into)
Condition: Compare two values
Check if {{issue.description}} matches the regex:
{{issue.description.match("\*Application Name:\*\s\*(AWS)\[\w/.\_-]\*").first}}
Action: Create new work item in VST
Issue Type: Same as the original work type
In the audit log I see this error:
Create Work Item 21/05/2025, 15:58:43
Error retrieving the work type fields for project/typeId – 10289/10495
I’m 99% sure it’s failing because I have a custom “Work Type” field on this issue. Does the order of steps look correct in general? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nikusha Kalatozi ,
Looks good!
Supposedly this issue occurs when trying to fill a customfield with an incorrect smart value;
Double check all input when creating the new work item, see where it goes wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nikusha Kalatozi , you could simply use an If/Else condition but possibly using a table would be better. New-Automation-action-Create-lookup-table
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.