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; } } }

Need help in Automation

Rahul_gb31nc

I have 2 projects in Jira A & B. I have created a automation rule in project A like when issue transitioned from todo to inprogress create an issue in project B and it's working fine(issue is getting created). Now my request here is when comments added in project A issue or automation ticket in project B, the comments should reflect in both the issues. I hope this is possible through automation. Need your thoughts on this

Accepted answers

Ste Wright

Hi @Rahul

This should be possible if there's a relationship between Issue A and Issue B - eg. a parent/child relationship, or an Issue Link.

---

For example, if I wanted comments to reflect on two issues linked using blocked / is blocked by, I could have:

Trigger: Issue Commented
Condition: Related Issues Condition
- Related Issues = Linked Issues
- Link Types = blocks, is blocked by
- Condition = Are present
Branch: Branch rule / related issues
- Type = Linked Issues
- Link Type = blocks, is blocked by
- Rule Restricted To = Project A, Project B
  - Branch-Action: Comment on Issue
    - Comment...
      {{triggerissue.comment.last}}
      
      Comment by: {{triggerissue.comment.last.author.displayName}}

---

A few notes:

You could restrict the rule using Rule Details to just Project A and Project B, to prevent unnecessary executions or accidental actions beyond the scope of the rule
In my example, the comment will be made by the Actor on the rule, Automation for Jira - that's why "Comment by" is required
But, you can change the Actor via Rule Details to be "User who triggered the event". This would make it the actual user for both the original comment and the automated copy. But they will need to have permission to make comments in the destination Project (Project A or Project

---

Let us know if this works for you!

Ste

All comments

Ste Wright

Hi @Rahul

This should be possible if there's a relationship between Issue A and Issue B - eg. a parent/child relationship, or an Issue Link.

---

For example, if I wanted comments to reflect on two issues linked using blocked / is blocked by, I could have:

Trigger: Issue Commented
Condition: Related Issues Condition
- Related Issues = Linked Issues
- Link Types = blocks, is blocked by
- Condition = Are present
Branch: Branch rule / related issues
- Type = Linked Issues
- Link Type = blocks, is blocked by
- Rule Restricted To = Project A, Project B
  - Branch-Action: Comment on Issue
    - Comment...
      {{triggerissue.comment.last}}
      
      Comment by: {{triggerissue.comment.last.author.displayName}}

---

A few notes:

You could restrict the rule using Rule Details to just Project A and Project B, to prevent unnecessary executions or accidental actions beyond the scope of the rule
In my example, the comment will be made by the Actor on the rule, Automation for Jira - that's why "Comment by" is required
But, you can change the Actor via Rule Details to be "User who triggered the event". This would make it the actual user for both the original comment and the automated copy. But they will need to have permission to make comments in the destination Project (Project A or Project

---

Let us know if this works for you!

Ste

Aleksandra Bosacka _Deviniti_

Hello @Rahul

It's Aleksandra from Deviniti, the vendor of the IssueSync app.

If you need to synchronize two projects either on the same or separate Jira instances, as an alternative to automation rules, you could set up a connection in our app which, based on selected triggers and JQL conditions, will automatically synchronize all tickets, also keeping the comments in sync

You can find the app here:

IssueSync - Synchronization for Jira

Cheers,
Aleksandra

Rahul_gb31nc

@Ste Wright Thank U. It worked

Umer Sohail _K15t_

Hi @Rahul , thanks for the question.

This is Umer, PMM for Backbone Issue Sync for Jira. Really wonderful to see that Jira automation can be so powerful and have so many use cases!

Automation works great for things like workflow triggers and comments syncing, but it can
eventually get cumbersome to keep manually creating and maintaining Jira automations.

If you need to automatically sync more Jira data in the future, you might want to look for a specialized Jira Issue Sync app, like Backbone Issue Sync for Jira.

Using Backbone, you can sync Jira issues and their corresponding data between two Jira projects. This includes Jira fields (including custom fields), comments, workflows, and attachments – even behind strict firewalls – without leaving your own Jira project.

Best of all, you can do this on Jira Software, Service Management, or Work Management projects on Jira Cloud, Server, or Data Center.

In case you're interested in learning more, feel free to schedule a free demo
or try Backbone for free for the first 30 days!

Regards,

Umer Sohail

Rahul_gb31nc

@Ste Wright my requirement had been changed. My comments should sync from Project A to project B(ticket created through automation) but the comments should not sync from Project B ticket(automated ticket) to project A parent ticket

Ste Wright

Hi @Rahul

You could do this by:

Changing the Rule Restricted To in the Branch to just Project B - and/or...
Limit the Condition / Branch link types to be considered

For example on (2) - if issues in Project A block issues in Project B, you might limit the Condition / Branch to just consider the "blocks" link type, and exclude "is blocked by"

Ste

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud