Copy Comment to linked Issue when new comment is added to original issue created

[Irina Lemus]

Hi,

I see this old solution https://community.atlassian.com/t5/Jira-questions/Copy-Comment-to-linked-Issue-when-new-comment-is-added/qaq-p/1604705 but it is not working for me.

What the "{{triggerIssie.comment.last.body}}:" is doing for me is passing blank comment to the triggering/original issue instead of to the cloned one.

What I want is that any comments added to the triggering/original issue are copied/passed to the new CLONED issue.

Here is my rule:

When rule is triggered : Comment is the maun action, Comment is added during status transition and Comment is added while editing the fields.

PROJECTS:I had both projects I am concerned about, also tried with just the original orject but it didin't work.

AND: Linked issues presents. TYPES: Is cloded by and Clones.

Then: Add comments to issue with "{{triggerIssie.comment.last.body}}:"

Please help and also with the howto for passing any attachments sent after cloning as well.

Here is the output

The Automation Log doesnt log a thing, although it is doing something...

Here is a fresher view, the rule details dont seem to get logged for some odd reason, although the output shows it is executing.

Thanks much! 

[Trudy Claspill]

Hello @Irina Lemus 

Looking at the text you provided, there is a typo:

Add comments to issue with "{{triggerIssie.comment.last.body}}:"

That needs to be triggerIssue rather than triggerIssie

If that is just an error in what you pasted into your post rather than an error in your Automation Rule, then please show us screen images of the actual rule.

[Irina Lemus]

Thank you for trying to help me. It was a typo.

Added the screenshot to the original post.

[Trudy Claspill]

Can you provide the output shown in the Audit Log for the execution of the rule also?

[Irina Lemus]

Added both. Thanks again @Trudy Claspill !!

[Trudy Claspill]

In the Audit Log there will be two types of entries. 

One type of entry is made when you change the rule and click the Publish button. Those entries show a status of "CONFIG CHANGE". That is the type of entry you've shown us.

The other type of entry is made when the rule executes. That type of entry will be made only if an event occurs that matches the Trigger and it happens in one of the projects specified on the rule's Rule Details page in the Projects field. The execution entries will have statuses like "Success", "Some errors", and "No Actions Performed".

Please show us the details of the most recent Audit Log entry that does not have a status of Config Change.

Also please confirm that the Rule Details page Projects field lists the same projects that you have in the second component of your rule.

Another thing to note is that when you use the Issue Commented trigger you can use the {{comment}} smart value to access the information for that newly entered comment. You don't need to access it through the triggerIssue smart value. You could instead use {{comment.body}}

[Irina Lemus]

@Trudy Claspill the rules details are not getting saved in the audit log, although the rule is getting executed. That's the point I tried to exaplin earlier. Is there any other way that  you know I could try to change this rule? Do you happen to have rules like this that work for you? If so, what are the parameters? The same or different?

[Trudy Claspill]

If the Audit Log for this rule doesn't show any executions, then I don't believe this rule is getting executed.

Sometimes there may be a short delay before the log entry is created for a rule execution.

To confirm which rule is getting executed, go to an issue where you believe the rule has executed.

1. Expand the Automations panel.

2. Click the Refresh button to reveal the most recently executed Automations.

3. Click on the link for the most recently executed automation. That will open that specific rule's configuration screen.

4. Click on the Audit Log link. That should show the log entry for the rule execution you clicked on in step three.

[Irina Lemus]

Interesting. I don't know why it wouldnt show the execution from the previous screen but I see how it is being successfully executed thru the ticket itself. Thanks for sharing how to find it.

Here is what I see. I changed the wording there to Cloned sisnce the Triggering wasn't working

and here is with the Triggering issue

[Trudy Claspill]

Jira doesn't prevent you from having multiple rules with the same name. Perhaps that is the case here and you were looking at the wrong rule.

The Audit Log of this rule says you are trying to use this smart value to add the comment.

There is no such smart value as {{clonedIssue}} so with this rule there will be no comment to find.

Please show us the details of the rule associated with this Audit Log.

[Irina Lemus]

@Trudy Claspill Hi! You are right. That smart value does not exist.

I got the rule to execute but it is now failing this comment "Comment on issue

Error adding comment to issue Comment body can not be empty (comment)"

Below are all the relevant screenst, LMK if I could provide another one.

Input ticket (Service Project)

Output ticket (Software Project)

[Trudy Claspill]

I see now that you are trying to use {{triggeringIssue

That also is not a valid smart value.

As I said in my first response you need to be using {{triggerIssue

[Irina Lemus]

Thanks for your patience @Trudy Claspill !

I changed the smart value to {{triggerIssue.comments.last.body}} and though the message is posted on the trigger issue, i need that same message to actually be passed to the "Cloned" issue, not the one in which the comment is already being entered. Here are the screenshots.

I entered the comment on PCW-5087 and expect it to be copied to OMS-70. However, the comment is copied on the same tirrgering issue, not on the cloned issue.

OMS-70 has no comments added. Is this fixable?

[Trudy Claspill]

I apologize. I failed to notice that there is a step missing in your automation rule.

You need to set up a For branch to drill into the linked issues to update them.

I recommend you structure it like this: