<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=344947) </details> <!--IssueSummary end--> <!-- Implementation issues are used break-up a large piece of work into small, discrete tasks that can move independently through the build workflow steps. They're typically used to populate a Feature Epic. Once created, an implementation issue is usually refined in order to populate and review the implementation plan and weight. Example workflow: https://about.gitlab.com/handbook/engineering/development/threat-management/planning/diagram.html#plan --> ## Why are we doing this work In #37322 we are adding `included_attributes` for all imported/exported properties, we believe that this will help us remove `excluded_attributes` section. In this issue we want to verify this and perform this change. > Since we're adding all these relations to the list of included attributes, does that mean we can clean up `excluded_attributes` list? Or do we need it for the duration of the transition? Since it's behind a feature flag, if I recall correctly. ## Implementation plan - [ ] ~backend Verify if removing fields from `excluded_attributes` will not affect import/export functionality and that these fields will be ignored during the import,