Automation between projects

[Edgar Pusklevic]

Hello , 
can automation be used like :
you create ticket in project X , ticket is cloned to project Y (with same fields).
Then you leave a comment in project Y , automation copy comment and paste it to project X. Then you leave comment in project X , automation copy to project Y.
Like API to both sides ?

[Walter Buggenhout]

Hi @Edgar Pusklevic,

Yes, absolutely. This just requires your automation rule's scope to be set to multi-project. Only your Jira Administrators can create and manage these so-called global automation rules.

Hope this helps! 

[Walter Buggenhout]

Can you point me to the right side , how to create that multiple-project scope ?

As I mentioned, you need Jira Administrator permissions to be able to do this. If you do, navigate to Global Automation in Jira Administration (can be found at https://<your jira site>.atlassian.net/jira/settings/automation#/rule-list), locate your rule and select Rule Details.

Right there you can select the rule scope and - for multiple projects - select the projects it applies to:

[Edgar Pusklevic]

Thank you for reply.
But there you can select two projects , but how your automation will work if rules are :
When issue is created -> clone issue -> to project Y ->...

so it means that in both projects will be same rule , if in project X task will be created it will be cloned to project Y and opposite. But I need that issue created only in project X will be cloned to project Y , with description and attachment fields.. and when in project Y new comment is added its copied to project X comments field , when answer to that comment is added as new comment it should be copied to project Y..
how we can make that ?
PS. I have admin permissions in both projects.

[Walter Buggenhout]

No. Just add a condition to your rule after your Issue Created trigger to validate which project the issue is created in. That would address the correct direction for the creation of tickets.

If you want to sync comments between issues, that would require a different automation rule because it needs a different trigger. Yet again, use conditions in your rule to determine what project(s) it fires from.

[Edgar Pusklevic]

can you please make automation and share print screen how it looks to make it in correct way..?
Thank you

[Walter Buggenhout]

Okay, @Edgar Pusklevic,

Since I can see you're struggling, here's a sample to get you started:

But do spend some time and effort to read through the automation documentation and experiment. We're users just like you who are happy to help you overcome problems and struggles, but not a free work force to do the work for you 😛 ...

These are very basic automation principles that you should familiarise yourself with if you want to start automating your Jira processes. Happy learning!

[Edgar Pusklevic]

Thanks !

[Bill Sheboy]

Hi @Edgar Pusklevic 

Yes, that is possible with a multiple-project scope rule.  Your Jira Site Admin will need to help set that up.

And the key is how do you relate the issues for finding them: an issue link, etc.  The rule could test in which project the trigger issue had a comment added and then use an if / else block to select the other project's issue to add a comment.

Please note well: some formatting (and the author, date / time, etc.) for comments cannot be preserved / copied in this way as the rule action does not support it.

Kind regards,
Bill

[Edgar Pusklevic]

Can you point me to the right side , how to create that multiple-project scope ?