Fields we created not showing up in custom fields so I cannot get them to show in other projects

Genevieve Orford
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2025

I've got a Team managed project (call it Project A). I'm trying to move epics / tickets from this project into another project (call it Project B) without losing information.

There are fields in the issues in the Project A that are not currently in the Project B so I want to add these fields to the issue types in Project B. However, I cannot find these fields in the 'custom fields' list so I cannot add them to issues in Project B.

 

Any ideas where these fields might be managed so that can edit which projects / screens have access to them?

4 answers

2 accepted

3 votes
Answer accepted
Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 6, 2025

Hi @Genevieve Orford ,

Welcome to the Atlassian Community.

Team-managed custom fields are independent from the the global custom fields. You will need to create the custom fields again in the team managed project.

Best regards,

Kris

 

Laura Humphries
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 6, 2025

+1, you were fast!

Like John Funk likes this
0 votes
Answer accepted
Sirine February 18, 2025

Hi @Genevieve Orford ,

The issue you're encountering is because Team-Managed Projects create custom fields that are specific to that project only. These fields don’t appear in the global Custom Fields list, which is why you can’t add them to Project B.

To resolve this:

You’ll need to manually recreate the custom fields in Project B to match the ones in Project A. This ensures the fields are available in the new project.

I have other solution that with it you can avoid these types of errors and manual settings every time : 

If you want to use custom fields across multiple projects (both Team-Managed and Company-Managed), consider using Colored Label Manager. It allows you to create global fields that can be used in any project either team-managed or Company-managed projects . 

This way, you can maintain consistency and avoid losing information when moving issues between projects.

Let me know if you need further assistance!

0 votes
Genevieve Orford
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 7, 2025

Thanks @Laura Humphries @Kris Dewachter for the welcome and speedy answers!

Yes they were created via the Team managed project. Sounds like we'll have to re-create if we want to move then 🫠 good to know

 

 

0 votes
Laura Humphries
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 6, 2025

The custom fields in project A, were they created only in project A? As team-managed projects where custom fields were created for the project itself cannot be shared with other projects.

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events