Updating an Issue in 2 projects at the same time.

[Ryan]

Hello,

I need to Issue getting synced in 2 different projects at the same time.

for example, when an issue clone is moved from CRM project to Tech project, they sync with each other so that when the issue is closed in Tech project, Automatically its clone gets closed as well in CRM project.

Thank you all for helping me.

[Walter Buggenhout · Accepted solution]

Hi @Ryan and welcome to the Community!

If it is just the status update (and a limited number of fields) that you want to sync, it is best to create an issue link between the issues when you make the clone. Once these issues remain linked, it is relatively easy to use automation to sync the status updates between both issues.

Set up an automation rule and make sure that it runs across both projects (in the rule details set the rule's scope to multiple projects and select the projects involved). It should have the following elements:

• Trigger: issue transitioned (to status closed (or any other status of your choice)
• Branc: for related issues (choose linked issues and optionally even add the type of link you use to identify your cloned issues)
• Action: transition issue (set the desired status)

Hope this helps!

[Ryan]

Hi @Walter Buggenhout 

Thank you very much for taking the time to help me.

I have used many automation both with my creativity and proven ones on the site.
but I keep getting the same error over and over:

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)

I have searched and done many things to resolve this error, but they did not work.

If you have some suggestions or have faced the same situations, I would be more than thankful for your help :)

[Walter Buggenhout]

Hi @Ryan,

You need to make sure that the workflow your issue is using does have a valid transition from its current status into the destination status you are trying to set (1)

if the issue currently is in status To Do and your are trying to close it while there is no transition from to do to closed, you will get an error.

While using a smart value may seem like a good idea, very often it is not (2) Especially when you are working in team managed projects, statuses that have the same name are actually different statuses across different projects. If you know what workflow your destination issue is using, it is better to select the expected end status from the list of available statuses in your transition issue action.