Having trouble populating field values in sub-tasks created via automation

[Ranjitha Rajendran]

Change Request:

We have a custom field on the Change Request form called Change Group. This field is an Assets field with multiple group selection enabled. Based on the values selected in this field, we use an automation rule to create sub-tasks under the main Change Request.

For example, if a user selects two groups, two corresponding sub-tasks are created for the approval process. Up to this point, everything is working as expected using Jira Automation.

However, I am facing issues when trying to populate certain fields in the created sub-tasks. Specifically, I want to:

• Populate the Change Group field in each sub-task with its respective value
• Automatically populate the Resolver Team based on the corresponding sub-task

I am finding it difficult to map and set these field values correctly for each sub-task. Any guidance or best practices on how to achieve this using Jira Automation would be greatly appreciated.

[John Funk]

Hi Ranjitha - Welcome to the Atlassian Community!

Can you please share the rule that you have so far including the details of the creation of the subtasks? That way we can provide better feedback. 

But basically you want to copy the value from the trigger issue. But first add a Re-fetch action after the trigger action so the work item has time to stabilze. 

[Marc -Devoteam-]

Hi @Ranjitha Rajendran 

Welcome to the community.

This could be tricky, based on the amount of options that can be set in this field. AS we can't copy the value, we need to set it based on the key of the assset object.

As @John Funk mentions, a view of the rule and the details of the rule components will provide more context