⚠⚠ 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.
Hey Everyone! Simeon from the Automation team here. I'm delighted to share some new features and improvements that we are shipping to Jira automation (Cloud only). Firstly, @Sam Harding ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events