How to match stages of cloned/original issues inbetween projects that are team/company managed?

[carolina]

Hello!

I'm trying to create an automation that will automatically transition a cloned issue's status. 

Eg: I have an issue in project CSCUST (team-managed) and I cloned the issue to project DIOV3 (company-managed). When I move the issue in project CSCUST to "closed" I want the issue in project XYZ to also move to closed, and vice-versa for all stages.

This is what my rule looks like:

The stages in both projects have identical names, but the workflows are not the same, since one is a team-managed and the other is a company-managed project.

Whenever I test the automation I have an error message:

I'm almost sure that this is because of having different workflows, but I wanted to check with the community... if this is the case, how can I apply the classic JIRA workflow that DIOV3 has, to CSCUST which is team-managed??

Thank you!!

[Yogesh Mude]

Hi @Stephen Farrell

Welcome to the Community!

It could happen when this email address is in the bounce list to Atlassian. 

This happens so your mail service doesn't lower Atlassian's emails reputation, which could degrade the quality of service of JIRA Cloud.

So please try to contact Atlassian Cloud support they will help you out.