### Release notes Show import results to more users than only the migrating user, making import history accessible to all group owners. ### Problem to solve Currently, import results are visible only to the migrating user. This creates an impediment when multiple people in a company are involved in the migration process and need to audit its results. As we're allowing group owners to see the placeholders tab and re-assign contributions, we should also allow all group owners to see import results for the groups they own. Additionally, only the group owner who started the import currently receives the email notification about completed imports. When we change this so all owners can see results, they should all receive the email, as imports represent important changes to their group. ### Proposal Add "Import history" to the Group sidebar - this should be visible for all group owners and administrators when they navigate to this page. We will have two distinct import history pages: - "User import history page" - under "Your work" menu - "Group import history page" - under "Group" menu The importing user will be shown a link to the "user import history page." `Import history` under the Group sidebar should point to the import history for the group, visible only for group owners and admins and showing all imports to this group, regardless of whether the group owner was the migrating user. `Import history` under Your work sidebar should point to the "personal" import history - showing all imports for the current user (Your work - your imports). If the user deletes an imported project or group, the import record should remain, even though the group was later deleted. We will show the original destination path, and in case the group is deleted, also mention that it was deleted. This helps clarify when deletion was due to user action rather than a transfer/import problem. We would disable the destination link and add a "deleted" status. When a user transfers an imported group to a different top-level group, the import history record is still shown. If a user imports multiple times from the same source, we will maintain separate entries. Users will see different destination paths if they import the same project or group multiple times. #### Data retention policy We will keep and show import history of last year - 12 months rolling. #### Showing results in sub-tabs At first, we will separate the results via tabs by the type of importer. We will have one tab for Direct Transfer, another for Project Import (both File-based and Third Party), and one for Group file-based. This is [not ideal](https://gitlab.com/gitlab-org/gitlab/-/issues/524809#note_2430831201), but it [will make BE implementation easier](https://gitlab.com/groups/gitlab-org/-/epics/17360#note_2433110376) for first iteration. https://www.figma.com/design/c67Fu98Fxcrn7uTR234GXm/Import-and-Integrate-follow-ups-from-17.9?node-id=4-26241&t=RSOTwQdbBwro3n9k-1 Names of the sub-tabs need to be updated.  ### Intended users - Group owners - Administrators - Migration managers ### Docs Update documentation on import history page in DT docs and project import docs. Talk about personal and group import history pages, who they're available for and where they can be found. Update docs on who receives emails (all group owners). Iterate what's shown on the import history page: all imports, also repeated, later deleted or transferred (moved to another group). Talk about retention policy and sub-tabs. You can start with: \_The system maintains import records even if imported projects or groups are later deleted, clearly marking them with a "deleted" status. If imported groups are transferred to different top-level groups, their import history remains accessible. For personal tracking, users can still access their individual import history through the "Import history" option under the "Your work" menu, showing all imports they personally initiated. To help organize import results, we've structured the interface with separate tabs based on import type. You'll find dedicated tabs for imports by direct transfer, project imports (covering both file-based and third party imports), and group file-based imports. This tabbed approach makes it easier to locate specific import records based on the method used. We've also implemented a data retention policy that maintains import history records for a rolling 12-month period, ensuring you have access to a full year of import activities while keeping the interface focused on relevant, recent data.\_ ### Feature Usage Metrics Track number of visits to group import history page by: 1. Migrating users 2. Non-migrating group owners 3. Administrators #### Success metric 1. **Target:** 30-40% of import history page views come from non-migrating group owners/admins  Table component MR -\> https://gitlab.com/gitlab-org/gitlab/-/merge_requests/180098 Table component in StoryBook -\> [http://localhost:9002/?path=/story/vue-shared-import-import-history-table--default](http://localhost:9002/?path=/story/vue-shared-import-import-history-table--default) Figma file with workflow -\> https://www.figma.com/design/8SyoJ7QPtz7CWhOtq5hAcz/%F0%9F%A4%94-Miocene's-ideas-exploration?node-id=1977-16276&t=cHJ4vk7MRvY4yCR7-1 Figma file with this issue -\> https://www.figma.com/design/c67Fu98Fxcrn7uTR234GXm/Import-and-Integrate-follow-ups-from-17.9?node-id=4-2299&t=okoHIOWCznpLubO9-1 Ask @jmiocene if you have any questions or for gitlab~2024184 reviews. **IMPORTANT NOTES** For users, the main proposal is to merge project and group import histories into one. There could be two different paths for group history page: 1. You can add a group DT history page and later consider adding projects here too. 2. Show only groups here, if it's not necessary to show project imports here too.