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
⚠⚠ Since getting involved with the new Product Discovery template in Jira Premium cloud, We now have an confusing and automation ruining situation.
The Product Discovery "Team" field is available in the "Edit Issue" action in Automation for Jira, but this confuses the existing "team' fields JSON that we use to populate the team field based on Reporter.
Note: In the below screenshot I have added the "Team" field and populated with the Product Discovery demo team entries as well as leaving our (shared) Team JSON in the additional fields section. But the highlighted error occurs regardless of whether the "Team (checkbox)" field (as JQL calls it) is selected or not.
I've raised this with the Product Discovery folk, but wanted to make the Automation for Jira community aware of the confusion (and potential breaking of Automation rules) associated with the introduction of a second field call "team" when you evoke a Product Discovery template/Project.
I have suggested they consider changing their "Team" field to "Teams" seeing as it is a multi-select and the Advanced Roadmaps based (shared) Team field is not, to help avoid confusion.
Note: How they in JQL below
Hopefully this is a helpful warning to others and hopefully can be resolved soon, as other than this situation Product Discovery is a very cool new addition to the Atlassian suite.