Need help on defining the email content for automation

[Sanjay Dangi]

Hello All, 

First of all, Apologies for the quality of picture

I have created an automation so as to get a notification whenever a new jira issue is added to a closed or cancelled epic. 

The automation is working for me. However, I am looking for below four informations in the mail:

1.  Impacted EPIC :  closed/ cancelled epic that was added with new jira issue

2. Triggering Issue : issue that triggered this automation

3. Creator : whoever triggered this event

4. Moved/ cloned/ created : whether the triggering issue was moved from other epic/project or it was cloned from the existing epic or it was created new. 

While I am able to take care of the first 3 points. Need help with #4, if at all any smart value that i can use for this? 

Thanks, 

[John Funk · Accepted solution]

Hi Sanjay,

I would create two separate rules - that should make number 4 very easy then. You can add it to the existing one, then copy the rule and adjust for the other trigger. 

[Sanjay Dangi]

Hello John, 

What do i need to do to create a separate rule for 4? If you can guide me please

[Bill Sheboy]

Hi @Sanjay Dangi 

In addition to John's suggestions...

There are two errors in your current rule in the Send Email action's content: in the triggering issue line, the URL and summary are instead referring to the Epic as they are missing the {{triggerIssue}} prefix.

Consider changing that line to this:

Triggering Issue: {{triggerIssue.key}} {{triggerIssue.url}} and summary - {{triggerIssue.summary}}

Kind regards,
Bill

[Sanjay Dangi]

Thank you bill for the suggestions. 

Could you also suggest as to how should I go for #4!! 

Thanks again, 

Sanjay

[Bill Sheboy]

First thing, I am using Jira Cloud and not Server / Data Center, and that is what you are apparently using.  Please investigate your version and test accordingly.  With that out of the way...

When using the multiple events trigger as you show, the rule has less information available.  Try using the specific triggers to gain more information...

If you use the Issue Moved trigger instead, you at least know the issue was moved from another project.  For Jira Cloud, the smart value expression {{#changelog.project}}{{fromString}}{{/}} will indicate the source project.  I do not know if that works for Server / Data Center.

When issues are Cloned with Jira Cloud, a clones link is added.  If that also applies with Jira Server / Data Center, the link could be used to identify the source issue when the Issue Created trigger is used.

[Sanjay Dangi]

Thank you Bill