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; } } }

Trying to update "Team" values on child tasks from Parent

Damo_xogtig

We have teams which appears to be a custom value, and was able to identify the JSON value of this based on other articles.

However, when creating tasks under a parent/epic, which usually has the team set, would like an automation to auto populate this field.

However, when I run attempt to test the rule, am getting the following error:

I assume have something screwed up with the branching logic, any assistance is greatly appreciated.

Accepted answers

Evgenii

Hi, @Damo

Welcome to Atlassian Community

According to your requirements - you want to update Team field in child issues, but your rule makes opposite. You're trying to update Team in epic issue.

It's example of working rule:

All comments

Evgenii

Hi, @Damo

Tomislav Tobijas

Hi @Damo ,

Can you share some additional info such as which field type is this field "Team"? Is this the system Team field or are we talking about something else?

❓Although, I'm wondering - are you trying to copy Team value from parent to newly created child, OR are you trying to copy value from newly created child to parent?

If it's in fact a custom field, you could maybe use issue field condition together with the copy option within edit issue action. 👉 Note that this, as you're in the branch' will copy the parent value from child to parent/probably Epic (as the trigger issue is the child one).

If it's a system field, you probably won't be able to select it within condition, but you can use something like the following JQL query/condition:

"Team[Team]" IS NOT EMPTY

and advanced issue editing section as you did in your example.

Cheers,
Tobi

Damo_xogtig

Thanks, was able to get this working using the above, seems like I was making it more complex that it needed to be.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-automation