Issue Summary

While trying to set up automation to copy the comments for issues that are cloned between projects, some of the comments are missing in the newly created (cloned) issues in the destination project.

Steps to Reproduce

Please note that this is the scenario that was used to replicate the behavior, but the same behavior might apply in other scenarios as well.

1. Create 10 issues and add 6 comments to each, including a comment with an attachment added to it.
2. Follow the Copy comments from the original Jira issue to a cloned issue article to set up an automation rule that is going to copy the comments between the original/cloned issues.
3. Clone the issues between two projects using a second automation rule, while ensuring that the issues from the source/destination projects are linked (to match the rule from the 2nd point above). 
4. On some occasions, you might need to repeat the above steps 2-3 times to stumble upon the issue.

Expected Results

All the cloned issues should have 6 comments added to them, including the ones with an attachment.

Actual Results

The results are inconsistent; some of the cloned issues are missing some of the comments, and there's no visible/logical pattern explaining the missing ones. Even if a delay and re-fetch issue data actions are added to the rule copying the comments, it doesn't change the behavior.

Workaround

Currently, there is no known workaround for this behavior in terms of Jira as-is, but it's possible to achieve a static/expected outcome using ScripRunner listeners.

A Jira-related workaround will be added here when available.