nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to auto populate custom fields in subtasks from parent ?

Ana-Rita Silva_f8oo8w

Hello,

I've created a Task with a set of subtasks that is cloned every time we onboard a new customer.

We designate the customer and product type at the task level but this doesn't auto-populate the subtasks.

I've played around with automations but I can't figure this out. I'd like for the customer and product fields in the subtasks to be updated by the same fields in the parent task.

Thanks!

Accepted answers

Bill Sheboy

Hi @Ana-Rita Silva

Would you please post an image of the rule(s) you have tried? That will help the community give you ideas.

Of note: if you allow the automation rule to create the sub-tasks rather than from cloning, the fields could be copied from the parent task when created. For example:

Trigger: issue created
Condition: issue type is task
Action: create subtasks, editing the desired fields to copy from the triggering issue task

Best regards,

Bill

All comments

Bill Sheboy

Hi @Ana-Rita Silva

Would you please post an image of the rule(s) you have tried? That will help the community give you ideas.

Of note: if you allow the automation rule to create the sub-tasks rather than from cloning, the fields could be copied from the parent task when created. For example:

Trigger: issue created
Condition: issue type is task
Action: create subtasks, editing the desired fields to copy from the triggering issue task

Best regards,

Bill

Ana-Rita Silva_f8oo8w

Screen Shot 2021-03-15 at 5.55.56 PM.png

Ana-Rita Silva_f8oo8w

Hey Bill,

Here's all I could do with what was provided.

This will only work if the subtasks are created after the issue is first created with the fields filled in.

In our workflow, we clone a master template task and set of subtasks (to be used for a customer onboarding process). All of the subtasks are created before we change the custom fields so this logic doesn't work. I can't think of another way given the constraints here to auto-populate. Maybe at task level transition from backlog to to do?

Thanks!

Bill Sheboy

Thanks for that information, @Ana-Rita Silva

Would you also please show the details of your Edit action?

You will find that for each field, you may select the ... on the right and select to copy the value from the Parent issue. Have you tried that?

Carla Olynyk

I see this. "Can't find issue to copy from"

Bill Sheboy

1) What is the issue type of ITSD-136, as I do not see you testing it with a condition in the rule? That error message, "Can't find issue to copy from", can occur when an issue cannot have sub-tasks, such as running the rule manually for a sub-task. I recommend adding a condition after the trigger to test the issue type.

2) As I noted, this could be a timing issue, although that is unlikely with a manual trigger. You could try to add a Re-fetch action immediately after the trigger and see if that helps.

3) What is the project type: company-managed or team-managed? This symptom appeared in the past for team-managed projects and was fixed with this issue: https://jira.atlassian.com/browse/JRACLOUD-75742 If it is still occuring, please ask your site admin to submit a defect to the support team: https://support.atlassian.com/contact/#/

Esther Wien_a5ng60

I had a similar problem and the re-fetch did the trick for me.

My steps:

When Issue created
Then: Re-fetch issue data
And: Edit issue fields
(Add Labels from Parent issue)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

atl-gruland