You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have written a Jira Automation which is doing well for all fields except one, which is the 'Team' field (which we got when we upgraded to Jira Premium).
As this field is not directly available in the fields for Automation related action. I used the 'Additional fields' section to populate the Team that is allocated to the Parent issue (Initiative which is defined as parent to Epics) to the Child Issue (Epic Level) which this automaton is creating successfully.
It works for all other fields but Team. I have tried the Custom Field ID for Team as well but I get the error 'invalid Jason'. Can anyone please help what is the correct JSON here???
Try using Branching Option and use trigger issue code in edit issue in branch action item.
In Branching you can select JQL and filter the required result. If You can share your Automation I will be able to guide you more on it.
Adding on to Mohammed's answer...
You note the "bit not executing" is what you have shared, but the rule you show does not attempt to set the Team field. Have you posted the correct image?
Next, there are unfortunately several fields in Jira Cloud named "Team" and many of the fields related to Advanced Roadmaps/Timelines are not supported by automation rules. I encourage you to use this how-to article to confirm your field is supported by automation rules before proceeding.
Essentially you identify an issue containing your field, call a REST API function with a browser tab, and then search for your field. If you find it, the field is supported and you can learn the correct smart value or custom field id to use. If the field is not listed, automation rules do not support it.