Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JIRA automation to create Issue Type Initiative basis of Epic

Arvind
Contributor
May 29, 2025

We use a JIRA structure of Initiative > Epic > User Story. We have added a custom field 'Customer Name' at both the Initiative and Epic levels.

We need JIRA automation for the following scenarios:

  1. If an Initiative with the specified 'Customer Name' does not exist in the project, create both an Initiative and an Epic, using the provided 'Customer Name' when creating the Epic.
  2. If an Initiative with the specified 'Customer Name' already exists, create only an Epic linked to that Initiative, using the same 'Customer Name'."

2 answers

0 votes
Akhand Pratap Singh
Community Champion
May 29, 2025

Hello @Arvind ,

Automation for Jira will do the Job here.

Considering, your trigger pint to be When Ticket is created and "Customer Name" is a user field.

Based on above 2 Consideration please find below Automation Rule, which will do the Job.

NOTE:

In Automation Rule, under user condition, Approvers is to be replaced by "Customer Name" field and the specific role you are checking against.

My Portfolio epic is your Initiative

Css 2.pngCSS 1.png

 

These are based on my Consideration and Assumptions, these rules can be modified as per your requirement by changing trigger points or adding more conditions

0 votes
Piyush Annadate _ACE Pune_
Community Champion
May 29, 2025

Hi @Arvind ,
Have you tested or created automation that isn't working or having issues with? It would be good to let us know about that so we can help you to tweak it.

Question here is: What's the trigger? Where the custom name is which will check and trigger the actions?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events