nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation to copy comments across projects

Daniel Gavrila_xhc5hh

Hi, I have linked a project in Jira Service Management (JSM) to one in Jira. I want to copy comments across: so when a comment is made in Jira, I want it to appear in JSM and vice-versa.
I am using this configuration, and I have used multiple variants, according to other answers from this community, but the rule is not executed. The rule is set to Global. Screenshot 2025-06-23 at 19.17.15.png Screenshot 2025-06-23 at 19.16.26.png

Accepted answers

Trudy P Claspill

Hello @Daniel Gavrila

What information do you see on the Rule Details page for the Project Scope?

Per the Audit Log image you provided it appears that the rule is scoped to a single project; REX Bug Report.

If that is the case, then the rule will be triggered only when comments are added to issues in that project, and they can be copied to other issues only within that project.

To have a rule triggered by events in multiple projects, the rule must had a Multiple Project scope defined, and each project of interest must be named in the project scope.

To update linked issues in other projects also the project must have a Multiple Project scope defined, and each project of interest must be named in the project scope. The For Linked Issues action will consider only the linked issues that are named in the Project Scope of the rule.

All comments

Gor Greyan

Hi @Daniel Gavrila

Thanks for the answer.

There might be some reason why the automation will not work.

1. Check the all projects' Comment Permission. The actor should have permission to all projects.
2. In the Global Administration check, the rule is listed as "Global Rule".
3. Try to use the following body.

Comment by: {{triggerIssue.comment.author.displayName}} at: {{triggerIssue.comment.created}}
{{triggerIssue.comment.body}}

Trudy P Claspill

Hello @Daniel Gavrila

What information do you see on the Rule Details page for the Project Scope?

Per the Audit Log image you provided it appears that the rule is scoped to a single project; REX Bug Report.

If that is the case, then the rule will be triggered only when comments are added to issues in that project, and they can be copied to other issues only within that project.

To have a rule triggered by events in multiple projects, the rule must had a Multiple Project scope defined, and each project of interest must be named in the project scope.

Daniel Gavrila_xhc5hh

Hi, @Trudy P Claspill , the rule is set to Global as I was saying. I think the scope was showing up as just one of the projects because I added the comment on that one. I then added a comment on the second, so they both show up.
I have also tried an option with Multiple projects, naming the two I linked. The result was the same.
Screenshot 2025-06-23 at 19.49.10.png

Daniel Gavrila_xhc5hh

Thanks, @Gor Greyan
I do have permissions to both projects, indeed and the rule is set as Global. I have tried the body you have suggested, but unfortunately it still doesn't add the comment I have made on one project to the other. Each stays with its own set of comments.

Trudy P Claspill

Thank you for that additional information @Daniel Gavrila

In the Audit Log please click on the ">" characters on the right wherever they appear to expose all the details added to the log, and then share that information with us.

Screenshot 2025-06-23 at 9.56.37 AM.png

It is also important to note that the Actor of the rule is "Automation for Jira", so that is the user that must have permission to add comments in the projects in order for this rule to work.

"Automation for Jira" is granted permissions when this appears in the grantees of a permission:

Project Role (atlassian-addons-project-access)

Lastly are the projects both Company Managed or both Team Managed or one of each?

Daniel Gavrila_xhc5hh

Thanks for the help, @Trudy P Claspill - Automation for Jira is indeed granted permission to comment on both projects, which are (both) company-managed.
The arrows showed that the ticket I made the comment on does not match the condition. Screenshot 2025-06-23 at 20.13.02.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management