Automation rule trigger help

[Ann Rumenapp]

We use Jira premium, company-managed projects with a jira hierarchy as follows:

Level 4 = OKR (custom issue type)

Level 3 = Change Initiative (Custom issue type)

Level 2 = Epic or Change Event (custom issue type)

Level 1 = Feature or CCR (both are custom issue types)

Level 0 = All other standard issue types

All Sub-task Issue types

I need to write an automation rule to populate a field on issue create for issues that are children of the Change Event issue type and excludes children of the Epic issue type.  What automation rule trigger would you recommend for this?

[Trudy Claspill]

Hello @Ann Rumenapp 

@Dick 's answer is not quite right.

You said you want to populate a field when the issue is created. So your trigger would be Issue Created.

You said you want this to modify only issues that are children of Change Requests. For that you need to add Conditions after the trigger.

One Condition you need is confirming that your trigger issue has a Parent at all.

Use the Related Issues condition and set it to Parent Exists

Next you said you want to have this affect only the children of Change Requests, not the children of Epics.

Add another Related Issues Condition, but this time choose JQL and set it thus:

This will confirm that the parent of the trigger issue is a Change Request.

[Dick]

Hi @Ann Rumenapp 

You need to trigger on issue creation, then check if it's of the epic issuetype and check if it has a parent. If it does have a parent, you follow up by an edit action in which you fill the triggerissue's special field.

You should be aware that users might also set the parent link of an epic after creation. In this case you would need an additional automation that is on field change of the parent field, then check if we're talking about an epic. Only if it's an epic, you need to check if the the parent field is filled or empty, followed by editing the special field of the trigger issue if its parent field is filled. 

Kind regards,

Dick