Jira automation triggering twice for certain scenario

[Aisha M]

I have the below automation provided by Atlassian to clear the Parent Link when issue type is changed - 

https://confluence.atlassian.com/automationkb/automation-for-jira-how-to-clear-the-parent-link-field-when-an-issue-is-moved-to-a-new-type-1206795140.html

At times, when I look at the issue history, the parent link is cleared twice from the same issue. This happens only when the issue type change happens from Epic to Portfolio Epic. For all the other issue type changes, its clearing just once.

Our hierarchy is Portfolio Epic > Program Epic > Epic > Story 

Any thoughts on why at certain instances the automation is getting triggered twice ?

[Bill Sheboy]

Hi @Aisha M 

For a question like this, please post an image of your complete automation rule and the audit log details showing the rule execution.  Those will provide context to help explain this symptom.  Thanks!

Until we see those...

For an example issue with this behavior, if you view the history do you see the issue type changing once or multiple times?  That may explain the rule triggering multiple times.

Kind regards,
Bill

[Aisha M]

@Bill Sheboy Thank you for the comment. Unfortunately due to my org restrictions, neither can I take nor attach screenshots. The automation is the exact same as provided by Atlassian in the link in my question.

From the issue history, the issue type changes just once, after that event, there is two entries for 'Parent Link" being removed. Happens ONLY when issue gets converted from Epic to Portfolio Epic)

Below is an example of the audit log, (here the same below log is present twice as well)

Action details:

Advanced compare condition

The following issues passed:

ATZPS-1285

Re-fetch Issue data

Issue data re-fetched from server successfully.

Edit Issue

Issues edited successfully

ATZPS-1285

[Bill Sheboy]

Which user does the history indicate changed the Parent Link?

I wonder...as Portfolio Epic is the top level in your hierarchy if Jira is already clearing the field because it does not apply.  Perhaps there is some work in-progress for the defect for this symptom: https://jira.atlassian.com/browse/JSWSERVER-24811

The way to test that would be to disable the rule and try changing the type of a test Epic which had a Program Epic set as the Parent Link.  If the field is still cleared, Jira is doing this, and so the rule could be modified to add a condition and ignore clearing the field if the new type is a Portfolio Epic.