Concerns about the Team field

[Curt Holley]

I have already written to @Tanguy Crusson 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]

Thanks @Curt Holley !

For people here with that issue: you can rename the "Team" field to "Teams" and that should fix it.

We updated the project template with the same.

[Erin Mihalik]

@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.  

[Curt Holley]

Brilliant. So easy to fix. 

Now I can get back to loving Product Discovery.......and the weekend.