Is there any possibility that automatically synchronize story and task between two Jira projects?

[Donghua SHEN]

I've got a request recently to transfer and synchronize story and task between two individual Jira projects, details to be defined as:

• All historic stories and tasks cloned/synchronized between two Jira projects with consistent status.
• If task in project A changes, then automatically updated in project B.
• If new task created in project A, a cloned task show up in project B.

Is there any possibility to do these automatically by setting up rules to execute?

I know bulk move or clone tasks manually at one time can meet the first requirement, but there is no connection between two Jira projects and normally task status changed separately.

[Christophe De Beule]

Hi @Donghua SHEN

I am Christophe a solution engineer for Exalate.

With Exalate you can easily automate the process to sync over your stories and tasks between multiple Jira projects.

Through triggers this syncronization can easily be done automatically.

Exalate is easy and straightforward to set-up and you can control exactly which data you want to send and/or receive. 

When your issues are synced it will update any changes you apply into the other issues so you don't have to worry about missing anything out.

Please feel free to book a customized-demo with one of our solution engineers.

Kind regards,

Christophe De Beule

[Matthias Gaiser _K15t_]

Hi @Donghua SHEN,

as the two others said, you can accomplish this with an Automation.

If you want to use Automation for it, I'd recommend to add e.g. an issue link from the source issue to the target issue, so that you always know which issue should be updated later. Of course, instead of an issue link, you could also save the issue key as a custom field.

Automation works in my experience well for smaller scopes or unidirectional changes. It can be a bit challenging if you update issues on both sides simultaneously to write clever automation rules which can handle all these side effects.

If you're looking into an even more automated solution, have a look into issue sync apps on the Atlassian Marketplace. I'm part of the team behind Backbone Issue Sync and happy to answer more questions around our app.

Cheers,
Matthias.

[Kalyan Sattaluri]

It is possible through automation but you need to confirm if you have scope to include both projects in your rule.

If you dont have scope of both projects in automation but do have appropriate permissions on both projects, then you can use

- webhook trigger to "sync changes" and "clone newly created issues" between projects,

- A one time scheduled trigger with webrequest request to catch up to historical issues.

Providing details on these rules for webhook/webrequests is a long topic so if you have scope of both projects in automation, its the easiest route.

[BHUSHAN PATIL]

Hi @Donghua SHEN ,

Yes, it is possible by using Jira automation rules, you can automatically update issues in one project based on events in another project. You can create rules such as "When an issue is updated in project A, update the related issue in project B" or "When a new issue is created in project A, create a cloned issue in project B."

Regards,
Bhushan