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

The comments made in ideas in discovery project should be copied to the Delivery Tickets linked.

Venkatesh Bojja

The comments made in ideas in discovery project should be copied to the Delivery Tickets linked ("Is Implemented by") to the idea.
I wrote an Automation Rule to copy the comments from idea to the delivery tickets linked but here comes the issue.
There are few ideas / epics/ tickets "Relates to" this idea and all the comments are being copied to both the Delivery tickets and the "Relates to" tickets as well.

Below are the steps that i followed.
Solution: Restrict the Rule to "is implemented by" Tickets
Step 1: Modify the "Branch for Linked Issues" In the Branch Rule / Related Issues : Type: Linked Issues Link Type: is implemented by (only selected this, uncheck others). Step 2: Add a Condition to Filter Only "is implemented by" Issues Inside the Branch Rule, click New Condition → Select "Issue Fields Condition". Set: Field: Issue Links Condition: equals Value: is implemented by This ensures that only tickets with this link type receive comments. Step 3: Keep the Smart Values Condition to Prevent Duplicates Keep the Smart Values Condition to prevent duplicate comments: First Value: {{destinationIssue.comments.body}} Condition: Does not contain Second Value: {{comment.body}} Step 4: Comment on the Issue If the above conditions pass, proceed with the "Comment on Issue" action as before: **Author:** {{comment.author.displayName}} **Timestamp:** {{comment.created.format("yyyy-MM-dd HH:mm:ss")}} **Comment:** {{comment.body}} _(Copied from Idea Ticket {{triggerIssue.key}})_

Accepted answers

All comments

Bill Sheboy

Hi @Venkatesh Bojja -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help. Please post the following:

an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the rule details at the top, showing the rule scope
an image of the audit log details showing the rule execution
explain what is not working as expected and why you believe that to be the case

Kind regards,
Bill

Venkatesh Bojja

Image of complete Automation Rule.
Image of action,condition,braches
Image of Rule Details.

The idea in discovery project has one delivery ticket ("Is Implemented by" relationship) and one user story as "relates to".
If i add a comment in Idea, the comment should be copied to "Is implemented by" ticket only, it must not be copied to "relates to ticket.

Bill Sheboy

In your smart values condition, you reference the {{destinationIssue}} smart value, however that one is only available when using one of the issue linking triggers:

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-linked

I do not know that that value would even contain once inside of a related issues branch on linked issues, but the behavior is most certainly undocumented / unknown.

As you are trying to copy all of the comments added to the Idea into its linked "delivery tickets", I recommend removing that condition.

You seem to indicate that other link types are being found by the branch. Have you checked if those issues have multiple links (of different types) to the Idea?

Nick Haller

Hi @Venkatesh Bojja ,

I configured an identical automation, and believe I followed the linking you mentioned where:

JPD idea linked to Jira delivery through idea's Delivery tab
Other Jira work item is linked to JPD idea through "Relates to" link-type

But cannot seem to replicate the behavior you're describing where the automation is adding a comment to both the Jira delivery and other Jira work item. For example, here is my automation:

The idea, delivery and work item relationship:

But only the Jira delivery is commented on by the automation:

If possible, it might be worth connecting with JPD support to investigate further.

You can open a ticket HERE, or within JPD under the Give feedback tab >> Get help from the support team option.

Bill Sheboy

Hi @Nick Haller

Is the {{destinationIssue}} smart value available in rules for other than the Issue Linked and Issue Link Deleted triggers? There is nothing in the documentation to indicate this or what the value represents in other contexts.

Thanks, and kind regards,
Bill

Nick Haller

Hi @Bill Sheboy ,

As far as I'm aware of, {{destinationIssue}} is dependent on a link-type between two work items, ideas, etc.

I'm also unsure of whether or not there is any official documentation about this, but our knowledge base does have a handful of resources about how to use this.

Bill Sheboy

Thanks, Nick. All the listed articles you note which include that smart value use one of the link-related triggers. Guess I will experiment to see what happens :^)