Unable to link custom field to "Team-managed" project template screen

Question

Hi

I have created a single select drop down through JIRA settings/Issues/CustomFields. I proceed to associate that field to screens and wish to add them to projects that have been created using "Team Managed" Project template. However none of my team managed project screens appear in the link screen list.

Any project that is created with "Company Managed" template however does appear.

Am I missing anything? Is it not possible to do the above? Would hate to recreate the JIRA projects as Company Managed.

Sid

Carlos Faddul_kqcedv · Accepted Answer

@Siddharth Kumar usually fields in the "Team Managed" don't usually talk with the fields of "Company Managed"

Here is the doc: Customize an issue's fields in team-managed projects

"Fields in team-managed projects are contained within the project itself. Currently, you can't share a field created in one team-managed project with another team-managed project, or with company-managed project. Similarly, you can't use a custom field created in a company-managed project on your team-managed project issues."

I hope I helped you.

If this post was helpful, mark it as Accepted Accepted, so you can help others who may have the same difficulties.

If your question has not been resolved, please post again with more details.

Jack Brickey · Accepted Answer

hi @Siddharth Kumar , you don't add custom fields to TMP projects in that way. The custom fields under settings>Issues>Custom fields is for CMP. You add custom fields to TMP directly under the project > project settings > issue types.

Tessa Tuteleers · Accepted Answer

Hi @Siddharth Kumar ,

unfortunately for you, this page says it all:

Fields in team-managed projects are contained within the project itself. Currently, you can't share a field created in one team-managed project with another team-managed project, or with a company-managed project. Similarly, you can't use a custom field created in a company-managed project on your team-managed project issues.

The main differences between company managed and team managed can be found here, but the short version is; company managed is managed by the (admins of the) company, they can create configurations that can be re-used over different projects.

If you have a corner case of a project, that does not need those re-usable configurations, AND that has such special config (fields / flows / .. ) that you don't want to "litter" your instance with, you can consider using a team managed project.

Best of luck!

- Tessa