Automation rule not kicking in when changing issue to a sub-task

[david catriel]

Hi everyone

I'm trying to create an automation rule that will clear out certain fields when an issue is converted to a subtask, and the rule just doesn't seem to get triggered at all. Unsure what I'm missing. Any ideas?

I've tried using a condition to check the "Type" field itself for when it's changing value to "Sub-Task" as well as using smart values. Nada. Is a change to  a sub-task not considered a field change maybe?

[Hrvoje Reich]

I am seeing updates in confluence... I also noticed application links and after removing it activities are normal.. Is there a downside effect of removing application links?

[Javi]

It depends if you are linking Jira issues within Confluence pages and vice versa. By removing the application link to Confluence, you are also removing linking functionality. 

Here is a link to what functionality is provided by creating an application link between Jira and Confluence

See: Use Jira applications and Confluence together

Regards,
Javier A.

[Javi]

Hi Hrvoje,

What kind of activity are you seeing? If possible, could you provide screenshot(s) of what you see 

Additionally, make sure to check if you have any automation enabled or if any third-party plugins are making any changes to an issue. 

Lastly, make sure to see if you have any Application Links created to any other Atlassian Application to ensure that this is not a cause for the activity showing up. 

Regards,

Javier A.