I want to provide the cloned issue key summary , Description, Issue link via email notification

[suneel babu]

Hi Dear Community,

I Just want to Provide the Full details of Cloned Issue created by using automation rule.. The following are the mandatory ones,

1. Issue Key

2. Summary

3. Description

4. Issue Link
The above 4 points has to mention in the email body of the automation rule, I have alredy created the automation rule , but it has been giving the link of original issue link not the cloned one.
Kindly help me with the above syntax in the email body please

Thanks in advance,
Suneel Babu 

[Alex Koxaras _Relational_]

Hi @suneel babu 

Did you try to add a branch for the newly created issue before sending the email?

[suneel babu]

Hi @Alex Koxaras _Relational_ ,

Thanks for your quick Response,
 The automation rule , which I had created, given Screenshot below.

[Alex Koxaras _Relational_]

Use an advance branch before "And send email" and within this brach add this "send email" component.

Leave outside of the branch the "Permanently remove this issue"

[suneel babu]

Hi @Alex Koxaras _Relational_ ,

What are the Options I need to select after choosing the Advance Branch Option, & Can you pls tell me the Syntax of the email Which I need to provide in the automation Rule,

I mean , Subject, Description, what has to be in the body content ?? 

I knew, Its a silly question, Don't hesitate tell me, because I'm learner ..

Thanks ,
Suneel Babu

[Alex Koxaras _Relational_]

The branch rule would be this:

[suneel babu]

Hi @Alex Koxaras _Relational_ ,


Its not working as i expected


Thanks

[Alex Koxaras _Relational_]

Is the new created issue cloned to another project?

[suneel babu]

Yes,

User has to create the issues by using the customer portal-request forms/Types, Once issue has been created, by using automation rule  It will directly cloned to the some other Jira software project, and the project leader has to notified when ever new issue has been created.

Note: My application owner doesn't want to give customer portal access to the end users, He wants to give jira access only 

[Alex Koxaras _Relational_]

So why don't you use incoming mail handler to create issues directly to the 2nd project?

[suneel babu]

Why should  we go for such complex setting up of Incoming mail handler?

Instead , We should set up a simple automation rule, Which I had already shared in the above- screenshot.

It is successfully creating the issue in the JSM project and cloning the issue to the new project (Jira project ). Once cloned to the Jira project , deleting the issue in the JSM project as well.. It is working fine, 

My intention is .. The cloned issue details has to be sent to the Jira software project leader when ever new issue has been cloned in to his project.

I have given the email body Like this in the automation rule.

But it is picking the original ticket details in the email, Which was not picking the Cloned issue one

 

 

[Alex Koxaras _Relational_]

So adjust the project notification scheme (of the project where the clone issue is created) to include the Jira software project leader.