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!!

[Bastian Stehmann]

Hi @Siva R,

thanks for sharing your knowledge with us.

[Sai Sandeep Bandewale]

Thank you 

[shacharoz]

@Siva R @Bastian Stehmann 

sorry but i do not see this option. 

i am working on the online projectname.atlassian.net/jira

i do not see a "tools" section.

[Keeshan Raaj]

thanks for the guidance, was really helpful in making bulk changes.

[karim -Atlassway-]

Hi folks , 

Using Colored Label Manager you can Allow your team to define their labels, cleanup and organize them quickly with bulk powerful functionality .

Karim 

Atlassway Team

[lightning]

Thank you !

Note: In some cases you will have to select 'Open in Issue Navigator' before you see the option for Bulk editing.

[Chloé Vanhalwyn]

Thanks for this helpful and timesaver tip !!

[Aaron Haukedal]

Thanks for the help!

[Lawrence]

Thank you for sharing the knowledge. You've saved me a lot time.

[Deleted user]

Fixed.