Update Custom Field with Epic Name from Linked Issue

[Matt Baker]

Issues in our Support Project have a Custom Field named 'Target Fix Version'.  

When development is needed to fix a support issue an issue is created in a Development project and linked to the Support issue. 

Later when that Development issue is linked to an Epic I'd like to have Jira automation copy the Epic name to the 'Targe Fix Version' field of linked Support issue. 

How can I do this? 

I'm guessing that I need to use JQL and rule branches, but I just can figure it out.

We also have a Custom Field in the Support issue the contains the Development issue key (if that helps). 

[Rik de Valk]

Hi @Matt Baker , if the target fix version is a text field, you can simply set this field to the smart value {{issue.epic.summary}}. 

[Matt Baker]

I don't think that would work. The 'Target fix version' field is in the support issue. That issue doesn't get assigned to the epic. 

[Trudy Claspill]

Hello @Matt Baker 

What type of field is the "Target Fix Version" field in the support project?

What type of field is the custom field in the support issue where you store the development issue key?

What would you expect to happen if the development issue was

- reassigned to a different epic?

- removed from an epic and not reassigned?

Are you working with development issues in a Company Managed project or a Team Managed project?

[Matt Baker]

Both fields are text fields. I would want the 'Targte Fix Version' in the support issue to updated if the dev issue epic was reassigned or removed. This doesn't necessarily have to happen immediately. It would be ok to do this on a schedule. 

[Trudy Claspill]

Hello Matt,

You will need to construct a multiple project rule for this. That can be done only by a user that has Jira Administrator permissions, and from the System > Global Automation page.

You would need to set the Rule Scope to Multiple Projects and call out the projects where the Dev issue, its parent epic, and the service issue exist.

Are these all Company Managed (vs. Team Managed) projects?

Your rule can be written to detect if the parent Epic of an issue changes. You would need to follow that with a condition to make sure the child issue is in the expected project. You could then get the Epic Name from the parent issue.

Then you would branch to the service issues that are linked to the Dev issue and update each one with the Epic Name you got in the previous part of the rule.

You could also set up a scheduled rule that would walk through the service issues where the custom Development issue key field is not blank, and work from that angle back to getting the Epic name of the parent Epic of the Dev issue.