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

[Thiago Ribeiro [Adaptavist]]

Hey Hansi,

Firstly you need to create a filter based on the issue type bug and your developer as reporter:

issuetype = Bug AND reporter = "developer" 

Then you can use the Recently Created Issues Report

I hope it helps you!

[Chethana Hashani]

In my case, always bugs are raised after QA testing and hence, all bugs are raised by QAs. So always reporters of all bugs are QAs. So I think, I would not be able to use that filter :(

[Thiago Ribeiro [Adaptavist]]

So why do you need the rate for a particular developer knowing that he does not create bugs?