Ayuda con optimización de Automatozación en Jira Software.

[Keila Rivas]

Hola a Todos.

Tengo una automatozación en jira software, para qie cuando una historia (child) cambie el estatus a IN PROGRESS, la epica (parent) a IN PROGRESS tambien.

La automatización funciona solo cuando la última historia de la épica, se actualiza a IN PROGRESS, es decir, si la Epica tiene 3 historias, se cambia el estado de la Epica a IN PROGRESS cuando ésta tercera y última historia se activa a IN PROGRESS.

Necesito que la Epica se  actualice a IN PROGRESS cuando cualquier Historia de la Epica se activa, tenga una o varias historias.

Anexo jpg de la Automatización.
Agradecida por sus recomendaciones. 

[Trudy Claspill]

Hola @Keila Rivas ,

Elimine el paso marcado con un círculo en la imagen. Ese paso le dice a la regla que todos los problemas secundarios deben tener un estado de "En progreso" para que el Epic principal se cambie a "En progreso".

---

Hello,

Remove the step circled in the image. That step is telling the rule that all the child issues must have a status of "In Progress" in order for the parent Epic to be changed to "In Progress".

Help with Automation optimization in Jira Software.

Hello everyone.

I have an automation in Jira software, so that when a story (child) changes the status to IN PROGRESS, the epic (parent) changes to IN PROGRESS as well.

The automation works only when the last story of the epic is updated to IN PROGRESS, that is, if the Epic has 3 stories, the status of the Epic is changed to IN PROGRESS when this third and last story is activated to IN PROGRESS.

I need the Epic to update to IN PROGRESS when any Story in the Epic is activated, whether it has one or more stories.

jpg annex of Automation.

Grateful for your recommendations.

[Keila Rivas]

Thanks a lot Trudy

It's  Work! 

[Keila Rivas]

Please, 
I just only know have a little question, how can I run this automatization for all the epics no matter if they are new or old?

[Trudy Claspill]

Hello,

As long as the parent Epic is not in the In Progress status, and there is a valid transition available from its current status to the "In Progress" status, then the rule should work.

Note that the execution of the rule is when a child issue is transitioned from To Do to In Progress. The rule is not triggered by any event that happens directly in the Epic.

I'm not sure that I have addressed your question. If you think I have not, please provide more information about what you would want to happen with "old" versus "new" Epics.

[Keila Rivas]

Hi Trudy, Thanks Again!

I understand how the rule works.
I have epics prior to this automation, where the stories are "in progress" but the epic as such, is in "to do".

I think, I'm going to have to identify and update the epics prior to this automation, with a query.

If you have another idea, let me know.

Regards