Clone and sync issue

[Jacob]

Hi everyone,

I currently have 4 project that are setup using different workflows, fields, etc.

I was hoping to create a 5th project where issues created in the other 4 projects would be cloned into. I know I can do that through automation.

However, I do not see how I can keep the issues synced so comments, status, and other custom fields. 

Hope there is a genius that can help.

Jacob 

[Dhiren Notani_Exalate_]

Hi @Jacob ,

Thanks for posting your question here, this is Dhiren from the Exalate Team.

I would recommend you to try out a dedicated integration and synchronization solution like Exalate in this case as Automation can help you till some extent but not 100%. 

With the powerful groovy scripting engine provided by Exalate, you can choose to map the desired information between the two systems giving you autonomous control over both outgoing and incoming information.

Please feel free to reach out to me in case of any questions or concerns.

Thanks, Dhiren

[Mohanraj Thangamuthu]

Hello, Good day. You can configure automation rule to clone the issues and second rule can be created to sync the comments between these issues. Note, this will consume lot of execution and you might reach the monthly limit soon. You can also explore for existing Addons from marketplace.

[Diana_Architect_ZigiWave]

@Jacob hi there. I'll just add another option to the list that's already in the comments above - check out ZigiOps. 100% no-code integration tool, easy to deploy and customize to fit different use case scenarios. It offers advanced mapping functionalities - so you can control the information flow at all times and can automate crucial operations/tasks. Feel free to explore ZigiOps and see if it fits your needs.

Regards, Diana (ZigiOps team)

[Matthias Gaiser _K15t_]

Hi @Jacob

you're right, you can achieve some cloning and even syncing with Automation. If you want to that way, you need to create automations which listen for field changes and update the other issues correspondingly.

I'd use an issue link to keep the relation and then various automation rules which listen for changes and update the linked issue accordingly.

If you rather want to have an automated solution, check out the issue sync apps in the Atlassian Marketplace. There you don't have to deal with various rules, but only one configuration which fields should be exchanged. I'm part of the team behind Backbone Issue Sync. Feel free to also contact our support for discussing your use case.

Cheers,
Matthias.