How to automatically link newly created issues as child issues to specific epics

[Chris D.]

I'd like to know if there is a method to properly link issues as child issues to specific existing epics upon creation with the help of automation. For instance, a use case with the corresponding automation rule would be:

*Note: The existing epic name will be "Test-0001"

1. Create an issue with summary "Test-0001a" 

2. Compare this created issue with the existing epic "Test-0001"

3. Link the created issue as a child issue to epic "Test-0001" 

I have been dabbling using various approaches, however, I cannot seem to be able to come up with a correct implementation. These are the few implementations that I have been working with. The first one uses custom field value to compare to one another (noted by customfield_10384). Furthermore, the second rule has a smart value "varEpic" with a value of "{{#createdIssues}}{{key}}{{/}}" to refer to the created issue's key.  Thank you for your further help on this issue!

[Manoj Gangwar]

Hi @Chris D. , Welcome to the atlassian community. 

I tried below automation and it works as per your requirement. 

[Bill Sheboy]

Hi @Chris D. -- Welcome to the Atlassian Community!

FYI...the "For Similar Issue Description" branch was recently added for JSM projects, and "similar description" option needs to be enabled for the JSM instance for it to work.

Although that branch type also appears in rules for Jira Software projects, it does nothing.  Per an Atlassian post, there is a plan to make it work in the future and showing it in the rule editor is a defect.

Kind regards,
Bill

[Chris D.]

@Manoj Gangwar @Bill Sheboy 

Thank you for your assistance! 

Although this works for specified Summary text, I am hoping to find a solution that would essentially look at all the epics that are currently created and compare with the newly created issue/s. From there, I would like the created issue's summary to match with similar existing epic's summary and establish a link where the created issue is a child to the epic. 

I did realize in the audit log that the branch was not being passed on. Thank you for clarifying on this issue!