Remove "Permissions" and "Relationships Legacy" fields from the field selections sidebar in the Content Type editor

[john-thomas-dotcms]

Parent Issue

No response

Problem Statement

The "Permissions" and "Relationships Legacy" fields are now deprecated, and will not be migrated to the new content edit screen.

We need to prevent customers from adding these fields to content types which don't already have them, to reduce the work needed to migrate when the new content edit screen is delivered.

Steps to Reproduce

1. Create a new content type, or edit an existing content type.
   • Result: The deprecated fields still show in the list of field types you can select.

Acceptance Criteria

1. The Permissions field does not show in the list of field types to select.
2. The Relationships Legacy field does not show in the list of field types to select.
3. Both fields still behave normally for any content types which already have one or both of them. This applies to all of the following places at a minimum:
   • The Content Type edit screen.
   • The content edit screen.
   • Content pulls of legacy content types ($dotcontent.pullRelated).
   • Push publish.

dotCMS Version

All current versions

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response