Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Copy Comment to linked Issue when new comment is added

when I try try this, it will work for first comment added but future comments between my JIRA cloud projct and JSM project will not be added:

Comment1 config.PNG Commen Log.PNG


When I try using a branch with condition to linked issues  it will run in a loop and add multiple duplicate comments.


I simply want to add any new comment added from JIRA cloud ticket to linked JSM ticket.  If not JSM is useless to me as I dont want my team to have to maintain both JIRA and JSM tickets independently.

3 answers

1 accepted

5 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 09, 2021

Hi Tim,

From your screenshot, it appears that the "Prevent duplicates by only adding this comment once to a particular issue" checkbox is unchecked. However, the audit log message is the message that we provide when a comment is prevent _because of that checkbox_. 

That's actually a minor point as the configuration of your rule won't do what you're intending. A rule configured as in your screenshot will add a duplicate comment the issue on which the original event was triggered. That is to say, when a comment is created on issue A, if issue A has a linked "duplicate" issue, issue B, a comment will be added to issue A containing the contents of the latest comment on issue A.

I was able to create the automation that I believe you're after and have provided screenshots of that automation from my own instance.

Of note, two important pieces of configuration are shown:

  1. The prevent duplicate checkbox on the comment action component must be unchecked. This allows multiple issues to be moved from one issue to the other.
  2. The actor of the rule must be set to Automation for Jira to prevent the rule from creating a circular execution loop where a comment created by automation begits yet another comment being created on the other issue and on and on forever.

Screen Shot 2021-02-10 at 12.16.18 am.png


Screen Shot 2021-02-10 at 12.17.49 am.pngScreen Shot 2021-02-10 at 12.17.54 am.png


Thank you Wes.  I hope to become a JIRA Automation expert in the near future.  Very powerful.  I appreciate your time and excellent documentation of this rule.

Hi. I saw the above and I think it is exactly what we need, but I can't find these conditions in our Automation. Are they in the PRO version?

Hi @wwalser 


Can you check from my end? It doesn't seem to be calling the related linked issue from Jira Software:



I am also getting "No actions perfromed" when trying to update comments on our on Prem Jira from JSM (and vice versa). 

The action details states:  

Branch rule / related issues
No related issues could be found
Is it enough to have the application link set up or are there more permissions that needs to be set on the remote site? 

This is really helpful. 

I have an additional layer of complication, however:

I have an automation configured that when conditions are met on one board (O3O), it automatically clones the issue onto another board (LF) and links the issues.

From there, all action by employees will be done on the LF board.

  • Any comments made on the LF ticket trigger the same comment on the O3O ticket.
  • Any status transitions on the LF ticket to trigger a comment on the O3O ticket "The linked issue has been transitioned to In Review"
  • The closure of the ticket on LF to trigger the closure of the ticket on O3O.

Hoping you can assist. 

@Mark Toledo  I would assume that you are trying to copy comments to a linked issue in a different project. If this is the case you have to add this a a global automation fro multiple projects. This also counts against your global automation executions. 

1 vote
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 07, 2021

Check your comment rule to see if you have it set to not perform duplicate action. 


I have a problem that i can´t solve it.  By coping that secence i could copy the written comments but if in the comment there is an document atahced the file gives me an error while coping it (it dosen´t charge in the sub-task). 

I hope somone can help me to solve this issue.


Hi @Santiago Casaretto , I cannot find the source however it is a limitation from JIRA that attachments are not being copy by the automation.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events