Is it possible to update the Parent ticket's Component field based on the sub-tasks' Components

[Brett Dains]

Using JIRA Automation, I would like the parent ticket's Component field to be updated to reflect the sub-tasks' Component's field values when first configured and modified.

Example:

• Parent Issue: UI, API
  • Subtask 1: UI
  • Subtask 2: API

I have attempted to use both the 'Set Value' and 'Copy From' operations unsuccessfully.

• 'Set Value' will replace the parent's Component field with the specific sub-task being modified
• 'Copy From' using the 'Add to existing values', from the 'Trigger Issue' will append the modified Component but not remove any pre-existing Components no longer applicable
  • I have attempted not using the 'Add to existing values' which will replace with the single sub-tasks Component but not across sub-tasks

[Bill Sheboy]

Hi @Brett Dains 

One way to do this is with 2 rules:

1. Trigger as you did with a sub-task's components changing, and then clear the Parent's component
2. Trigger on parent's component change cleared by automation, branch to re-add all of the sub-tasks values.  Set the option for this rule so it can be triggered by other rules.

The key for this to work is a stopping condition: you need to handle the case where none of the sub-tasks have components, or rule (2) will keep firing.

I was pondering another method used by storing the previous sub-task's component, but there do not seem to be any logical functions with smart value lists that would support that.  If you can find one, maybe try that instead. 

Best regards,

Bill