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.
Hi, @Damien Wittmack
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:
Thanks, was able to get this working using the above, seems like I was making it more complex that it needed to be.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Damien Wittmack ,
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.