<!--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=500394) </details> <!--IssueSummary end--> This issue came from this discussion https://gitlab.com/gitlab-org/manage/import-and-integrate/discussions/-/issues/101#note_1976815398. ### About Currently, on [Group import_export.yml](https://gitlab.com/gitlab-org/gitlab/-/blob/e40420bfc7eed000f24d4bd54d3bc1809c85aa31/lib/gitlab/import_export/group/import_export.yml#L54) and [Project import_export.yml](https://gitlab.com/gitlab-org/gitlab/-/blob/ecaf61939432fe08eb7fa8fe48925d04c4685a68/lib/gitlab/import_export/project/import_export.yml#L789), both `excluded_attributes` and `included_attributes` lists need to be populated when a new field is added to a table. This is required because Import/Export and Direct Transfer weren't completely updated to use the `included_attributes`. We should work on updating both importers to use the `included_attributes` section. This is important for security reasons. We shouldn't rely on an exclude attribute list, which could cause an attribute to be mistakenly exported and make the code more consistent. We could move the `excluded_attributes` attributes to a spec test that checks if a new attribute was added to the table and informs developers whether to add it to the `included_attributes` list or exclude it from the spec file.