Link Issue as child to Epic based on field & summary

[Sushil Ranjan]

I am looking for the automation when Issue is created, it check for the field value component. If component has 'iOS1' then it should be add as child issue to the epic (already created) having summary 'this is epic for iOS1'. Similarly if field component is selected iOS2 during issue creation, it should be automatically added as child issue to Epic whose summary is 'this is epic for iOS2'.

Thanks in advance!

[Trudy Claspill]

Hello @Sushil Ranjan 

An issue can have more than one Component value at a time. What should happen if the issue has both component values?

Are the issue keys for the Epic known, or does the automation need to find the Epic based on the Summary?

[Sushil Ranjan]

Thank you @Trudy Claspill  for the response.
for now we have component - iOS1/2/3. We will train the users to select any one of the value. We will move to new single select list in coming days. But this is ok if users select more than one and rule fails.

As per current requirement, automation need to find the Epic based on the summary.

Thanking You!

[Trudy Claspill]

Let me repeat back what I think you want. 

1. When an issue is created
2. And it is an issue type that could be a child of an Epic
3. And it is not already a child of an Epic
4. And it has just one value specified in the Components field
5. Then find the Epic that has a Summary that contains the name of the Component
6. And if it finds exactly one such Epic
7. then make the issue a child of that Epic

Is that correct?

Will there only ever be one Epic that has the Component name in its Summary?

Will the Epic always be in the same project as the child issues?

The numbered items above are the steps of the rule

1 is the Trigger.

2 through 4 are Conditions.

5 is the Lookup Issues action.

6 is a Condition.

7 is the Edit Issue action.

Can you try building the rule based on that information and then show us what you create?