Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Inherit Object/Asset from Parent to sub-tasks

Gerda De Lima
August 3, 2026

Hi everyone,

I'm trying to create a Jira Automation rule that automatically copies an Assets/Object field from a parent issue to a newly created sub-task.

Setup

  • Field type: Assets/Object field
  • Field ID: customfield_12975
  • The field allows only a single object
  • Trigger: Issue Created (Sub-task)

Goal Whenever a sub-task is created, the value of the Customer Asset field on the parent should automatically be inherited by the sub-task.

3 answers

3 votes
Lalithesh Channu
Contributor
August 3, 2026

Hi @Gerda De Lima 

Hope this helps!

Automation set up:

  1. Trigger: Work item created
  2. Condition: Issue type equals Sub-task
  3. Action: Edit work item field
    1. Select your Assets/Object field from the list
    2. Select Copy Assets/Object field from Parent work item

 

Screenshot 2026-08-03 173400.pngScreenshot 2026-08-03 173431.png

 

Note: Please make sure the Assets/Object field is available on sub-tasks field configuration

If the sub-tasks are created by an automation, make sure to enable "Check to allow other flow actions to trigger this flow. Only enable this if you need this flow to execute in response to another flow" setting under flow details

1 vote
Cristian Quiroz Garcia - NTT DATA
Contributor
August 3, 2026

Hi! @Gerda De Lima ,

This is one way to achieve it:

  • Trigger: Work item created
  • Condition: Issue Type equals Sub-task
  • Action: Edit work item fields → Assets field using the smart value:
    key= {{issue.parent.customfield_12975}}

 Things to verify

  • Field ID: Make sure you're referencing the correct custom field ID for your environment. 
    key= {{issue.parent.customfield_12975}}
  • The key= prefix: This is the correct syntax for Assets/Object fields in Jira Automation. It tells the rule to look up the object by its key. 
  • Single-value field: As the blue info box in your rule confirms, if the AQL query returns multiple values, only the first one will be used — which is fine since your field only accepts a single object. 
  • Parent availability: The smart value {{issue.parent}} is only populated when the sub-task has a parent at creation time. If sub-tasks can be created without a parent, you may want to add an additional condition to check that the parent exists.

In this example i use the assets field "customfield_10131"

AUTOMATION_SAMPLE.png

0 votes
Gerda De Lima
August 3, 2026

Hi @Lalithesh Channu & @Cristian Quiroz Garcia - NTT DATA , 

 

Thanks for the quick response!

Have you had a chance to try this with Assets fields? It seems that the Edit Work Item Field action is not able to update an Assets/Object field.

I'd be happy to hear about your experience or if you've found a workaround.

Best regards,
Gerda

Lalithesh Channu
Contributor
August 3, 2026

Yes @Gerda De Lima

The field I've used in my automation rule is an Assets/object custom field

P.S. Please make sure the Assets/Object field is available on sub-tasks field configuration

Thank you!

Cristian Quiroz Garcia - NTT DATA
Contributor
August 3, 2026

@Gerda De Lima Yes — the example I shared does use an Assets/Object field.

The trick is passing the value with the key= prefix in the Edit Work Item Field action:

key= {{issue.parent.customfield_12975}}

This lets the automation resolve the Assets object by key and assign it correctly. Without key=, the field won't update.

Hope that clears it up!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events