Automatic change of status in parent task from a clone

[Tamara]

**Spanish below**

Hi, I have successfully created an automation to clone an issue from one dashboard to another (within the same project). What I am not able to configure is how to do so that when the status of the cloned task is changed( in progress, done, etc) the status in the task that triggered the clone is also changed.

Can someone help me? Thank you very much in advance.

Best Regards

Tamara.

----------------------------------------------------------------------------------------

Hola, he creado una automatización con éxito para clonar una incidencia de un tablero a otro ( dentro del mismo proyecto). Lo que no soy capaz de configurar es como hacer para que cuando se cambie el estado de la tarea clonada( in progress, done, etc) también se cambie el estado en la tarea que desencadenó el clon.

¿ alguien me puede ayudar? Muchas gracias de antemano.

Tamara

[Raffaele Saracino]

Hi at all,

I would like to solve the same issue but a little different scenario...

The created incident is ABC-123.

The cloned incident is XYZ-123, because the issue will be handled in a different project.

The goal is keeping both tickets up to date if comments and / or status changes in one of there issues.

[Trudy Claspill]

Hello @Raffaele Saracino 

Welcome to the Atlassian community.

Please start a new Question for your topic by clicking on the Ask a question button at the top of the community page.

Provide detailed information about your environment.

Is it Data Center or Cloud?

- If Data Center, what version?

What are the Types of the projects that contain the issues?

- If the projects are Company Managed, do they use the same Workflows?

Have you tried to construct the rule?

- If so, provide screen images of what you have and describe the part you are having trouble figuring out.

If you are new to Automation Rules I encourage you to take advantage of the free, on-demand training on that topic available at https://university.atlassian.com

Side note: Guidelines for this community state that necroposting (posting on issues older than 6 months) is discouraged.

[Trudy Claspill]

Hello Tamara,

Please clarify which issue's status change triggers an update to the other issue's status.

If you had issue ABC-123, and you cloned it to create ABC-456, would you want the change in ABC-123 to cause a change in ABC-456 or the reverse?

Would you want the status of the trigger issue copied to the other issue?

Are there any restrictions you would want applied to that scenario?

The basic structure for the rule would be similar to this:

In the For Linked Issues branch you would pick the link type (clones or is cloned by) that represents the cloning relationship between the trigger issue and the issue you want to update.

[Tamara]

Hi Trudy, 

Here is the real case:

The created incident is the ABC-123 , which has goes through the "validated" state of the flow and this state is the trigger for it to be cloned to the other board as the ABC-456. But the developer is going to work on this clone and it will go through states like in progress, blocked or done. I need the ABC-123 to change the state as it changes in the ABC-456 - have I explained myself better now?

Is there any restriction that I want to apply to this scenario, once the ABC-123 is cloned to the other board, I do not have any restriction.

I remain attentive to your answer

Regards

[Tamara]

By the way, the automatism to clone the issue when it goes to "validated" state is already done and working, I am missing the part where the cloned task, when it changes state, updates the original one also to the same state as the cloned one.

[Trudy Claspill]

Hello Tamara,

Thank you for that additional information. 

In that case you would want the Link Type selected in the second step to be "clones", not "is cloned by".

[Tamara]

Thanks, I will try that configuration.
I will keep you posted.

best regards

Tamara-

[Raffaele Saracino]

Hi at all,

I would like to solve the same issue but a little different scenario...

The created incident is ABC-123.

The cloned incident is XYZ-123, because the issue will be handled in a different project.

The goal is keeping both tickets up to date if comments and / or status changes in one of there issues.