- 
    
Bug
 - 
    Resolution: Unresolved
 - 
    
Medium
 
- 
        18
 - 
        Severity 3 - Minor
 - 
        1
 - 
        
 
Issue Summary
Team-managed custom fields are being displayed inside Company-managed projects when viewing the project settings. However, they are never available to be added to the issue view because they belong to a Team-managed project.
Steps to Reproduce
- Create a custom field inside a Team-Managed project
 - On a Company managed project, go to Project Settings > Fields
 - The TM project field will be displayed
 
Expected Results
As team-managed custom fields cannot be made available for use within a Company-managed project, they shouldn't be displayed in a CM project.
Actual Results
The field is displayed but cannot be used in a screen.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- duplicates
 - 
                    
JRACLOUD-74610 Next-gen custom field appear in the classic fields project settings
-         
 - Closed
 
 -         
 
- is duplicated by
 - 
                    
JRACLOUD-79845 Saved filter for the JQL breaks with when user create the same custom field name in Team Managed Project as of Company Managed Project.
-         
 - Closed
 
 -         
 - 
                    
JRACLOUD-81114 Company managed project's field configuration in project settings shows Team managed project's custom fields
-         
 - Closed
 
 -         
 - 
                    
JRACLOUD-82148 The 'Restrict to' field of the team-managed project is available for company-managed projects.
-         
 - Closed
 
 -         
 
- is related to
 - 
                    
JRACLOUD-76483 Standard custom fields are available to be edited for Team managed projects when using bulk edit
-         
 - Closed
 
 -         
 
- was cloned as
 - 
                    
JRACLOUD-94541 JPD fields are being displayed inside Company-managed field settings
-         
 - Gathering Impact
 
 -