Auto assign Epic Link when issue is linked to ProjectA BUT only when linked from ProjectB issues

[John Varela]

This is a pretty specific scenario. 

ProjectA supports multiple smaller projects, however when issues arise in one specifically smaller project, I want to auto-assign a certain Epic to the issue that gets created in the main project.

I've been able to easily create the basic functionality:

The challenge I'm facing is that I don't want this automation to run on any of the other smaller projects. Currently if ANY project issue links to ProjectA issue, that issue gets assigned the Epic (as long as the field was Empty).

What are some Advanced Compare Conditions I can use in the IF block to help me achieve what I'm looking to do? I'm not familiar with available values I can use to identify the source and/or destination issue's project.

I should also mention, we only use JIRA Cloud.

Thanks in advance!

[John Varela · Accepted solution]

Took me a bit of time but I was able to figure this out. Hopefully this will benefit somebody else!

I ended up needing two rules, both restricted to be used within ProjectA only:

1. Update the Epic Link field when the issue is created within ProjectA and later linked to ProjectB ticket
2. Update the Epic Link field using the Issue Created trigger
   • This supports issues being created via "Create Linked Issue" within ProjectB

Here are the two rules:

NOTE: The only reason "AND project = A" is needed in both of these rules while the rule itself is restricted to ProjectA, is due to ProjectA containing issues which belong to several different projects instead of just one, which isn't all that common.

If you want the rule to support multiple projects the same way (while updating multiple fields), here's an example: