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
Next: Root
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 already written to @Tanguy Crusson1 about this and warned the Automation for Jira community of the potential confusion concerning the "Team" field, but figured it makes sense to let this community know as well.
See post here for details: The Team field/s and Automation when using Product... (atlassian.com)
In a nutshell, if you have Jira Premium and use Shared Teams as part of Advanced roadmaps and have any automation around that field, introducing Product Discovery into your instance will introduce a second "Team" field, confusing the functionality out of Automation for Jira and potentially JQL as well.
Otherwise loving Product Discovery though 😍
@Tanguy Crusson In the perfect world, we would be able to use the existing Teams field from Shared Teams. It would make it better for automation, etc.
Brilliant. So easy to fix.
Now I can get back to loving Product Discovery.......and the weekend.