Global Team Field Auto-fill Logic

[Brandon Moberg]

Hello!

I'm trying to understand the logic behind the global Team field auto-populating on certain occasions in our Jira Product Discovery projects.

We have multiple JPD projects, and multiple views within each of those projects. From what I can gather, if you have the global Team field shown in the view, then when you create a new work item (Idea) from that view (regardless of which of the 3 create CTAs you choose to do so), the new Idea will inherit the Team field value from the view if the there is only 1 Team value utilized in that view (e.g., you're filtered to 1 team and/or the JPD project only has 1 team). But if there are multiple Team field values in the view or the global Team field is not shown in the view, then the Team value will not inherit a value upon creation.

I can't for the life of me find any documentation on this. Is there any documentation for this, and/or is my interpretation correct? 

Thanks!

[Tanguy Crusson · Accepted solution]

@Brandon Moberg that is most likely because of how the view you're creating the idea from is configured. 

if you create an idea in a view that has a filter "team = A", then this field value will be automatically applied to the idea - and that's how the idea appears on the view (otherwise it would be hidden immediately after you created it).

Can you check how the view's configured?

[Brandon Moberg]

@Tanguy Crusson that seems to check out. Is there a more efficient way to configure this functionality than relying on automation or a filter that can be temporarily changed by users? It would be ideal to be able to set the Team in the space settings to dictate whether or not the Team is auto-applied to ideas in that space.

[Tanguy Crusson]

Thanks for confirming @Brandon Moberg and for the additional feedback. It is not possible currently, but we're looking at design options to improve the idea creation experience and this fits part of that

[Jet]

@Brandon Moberg that's right, today the team field is an entity-based custom field that allows you to assign a specific team to an idea. Right now it doesn't offer multi-team linking but that's something we're aiming to improve.

You can find more info here: 

https://support.atlassian.com/jira-cloud-administration/docs/the-team-field/

[Brandon Moberg]

Hi @Jet 

The provided link returns a 404.

I'm not asking about multi-team linking. I'm trying to understand what drives the Team field to automatically inherit an existing team value upon issue creation.

[Christos Markoulatos]

Hi @Brandon Moberg 

I cant find any official documentation on this either. lets wait for the JPD team.