When an Epic is Linked to an Initiative, grab the Initiative's key into the Epic's custom field

[Keiko Kamiya]

I have epics that are linked to an Initiative and I am trying to set up an automation for when an Epic is linked to an Initiative, it'll grab the Initiative's key/summary into the "Initiative Key and Name" custom field into the Epic. However, I keep getting the error below:

No Actions Performed: 

Source issue (the main branch of the rule will execute for this issue and you can access it via {{issue}}):

EPIC-123

Destination issue (to perform actions on this issue use a 'Related branch', you can also access it via {{destinationIssue}}):

INITIATIVE-123

Is the set-up or smart values incorrect? Appreciate the help. 

[John Funk]

Hi Keiko,

Is the Initiative not the parent of the Epic? Did you setup that hierarchy? If not, why not? 

[Keiko Kamiya]

Hi John, 

The Initiative is from a JSM project and the Epic is from a Software project. I've encountered a similar problem. I am also trying to grab the Feature's key/name (from JSM as well) when an Epic is linked to it. It also wants the Initiative's key/name associated with the Feature. 

How it's set up:

JSM project: Initiative is parent to Feature

Software project: Epic 

Automation 2: Below works when I link an Epic to a Feature, it retrieves the Feature AND Initiative's key/summary

Automation 1: However, now the earlier set up I had when an Epic is linked directly to an Initiative is not working as expected: 

The reason why I have two automations is because I am trying to achieve: 

Automation 2: 

When an Epic is linked to a Feature, grab the Feature's key and the Feature's parent which is the Initiative key as well. This works. 

Automation 1:

When an Epic is linked directly to the Initiative, it instead populates into the "Feature Key & Name" field when it should populate the "Initiative Key & Name" field only. 

 If I disable/turn off the Automation 2, the Automation 1 works as expected. When they're both on/enabled, Automation 1 fires the wrong thing. 

[John Funk]

But if the Initiative is the parent to the Epic, just add the Parent field to the Epic screen. 

[Keiko Kamiya]

The Initiative is not the parent of the Epic. The Initiative is the "epic" in the JSM project and Feature is the child issue. 

The other regular Epic resides in the Software project. 

[John Funk]

I am confused. What is the Issue Type Hierarchy for your Jira instance?

[Keiko Kamiya]

Jira Service Management Project Hierarchy 

Level 1 = Initiative

Level 0 = Feature   

Jira Software Project Hierarchy  

Level 1 = Epic

Level 0 = Story, Task, Bug

I am trying to inherit the Initiative and/or Feature key/name when either:

1) Epic is linked directly to an Initiative (thereby Epic gets the Initiative's key/name) or

2) Epic is linked to a Feature (thereby Epic gets the Feature's key/name as well as Feature's parent= Initiative's key/name)

[John Funk]

NO, you can't have two different issue type hierarchies in a Jira instance. Can you share a screenshot of your Issue Type Hierarchy values? Settings > Issues > Issue Type Hierarchy. 

[Keiko Kamiya]

The lightbulb icon is the Initiative (in JSM project) and thunderbolt icon is the Epic (in Jira project); the Feature is in JSM as the hierarchylevel 0

[John Funk]

Ah, I see what you are saying now. There is still only one hierarchy, but you have Level 1 associated with multiple issue types. 

An Epic being linked to a Feature would simply be a done by issue linkage. Then you can achieve what you want based on the scenario. 

For the second one, the Epic would be the parent of feature in the most logical form. But you can also do that by an issue linkage. 

So, does the first automation cause the second automation to fire? Or are they completely independent? 

[Keiko Kamiya]

I think the below works: