Jira automation & Inheriting 'component' value from parent

[Anu Issac]

In Jira automation, I've set a rule that if children (story/task/bug/subtask) are created under a parent, the 'component' value should be inherited from the parent. This is working fine. However, if I add a different component that is not the same as the parent to the story/task, an error occurs. How can I avoid that?

[Sagar Mahajan]

Hi @Anu Issac Can you share your working automation details as if you not want to take any action when parent component is different than what it is selected for child issues then it need to be added in the automation rule condition to skip it when component is not matching the parent, if you share the rule, that will help understand what and where it need an update.

[Anu Issac]

[Sagar Mahajan]

@Anu Issac I created a below rule and it is working fine, not giving any error when other component is selected for child issues as automation rule keep the component added while creating the child issue and also copy the component from parent issue after the child issue created, so in this case child issues will have both the components one that copied from the parent and other that is selected while creating the child issue.