Automation - Custom field se cambia Principale non si aggiorna correttamente

[Stefano De Santis]

Ciao,

ho creato un campo custom chiamato "Stima Story" (campo numerico) ed eredita l'original estimate (in giorni) della story (tramite Automation); poi ho creato altre regole che fanno roll up sull'epica (principale) poi sul Work Package e poi sull'Iniziativa. Ho modificato la regola che, quando cambio epica alla story (quindi cambio il padre) la story modifica la "Stima Story" della nuova epica (es. se original estimate era 1 giorno questa si aggiunge alla nuova epica) ma contemporaneamente non viene tolto 1 giorno dal vecchio padre.

Vi metto gli screenshot della regola, sapete aiutarmi? Grazie

[Bill Sheboy · Accepted solution]

Hi @Stefano De Santis 

I believe you will need to separate this scenario into two rules: one triggered on a change to the Parent and one on a change to the custom field, "Story Estimate".  That will help with the special handling necessary for the change of the parent.

For example, the rule triggered on a change to the Parent could use the changelog smart value to update both the previous and new one based upon the changes with separate branches:

• the previous parent would use a branch on JQL expression with the changelog data
• the current parent could continue to use branch to parent

Please note well: your rules only handle cases for changes of fields.  But, there are several other possible ways the Parent or Story Estimate field could change and impact the sum.  To learn more, please see this article I wrote on summing / synching fields between parents and children:

https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Sum-or-Synch-Fields-with-Parent-and-Child/ba-p/3162890

Kind regards,
Bill