Add sub-issues to non-migrated list (#58858)

Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: 3 people

content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md

@@ -130,9 +130,7 @@ When you migrate a repository, either directly or as part of an organization mig
 
 Currently, the following data is **not** migrated.
 
-* {% data variables.product.prodname_codespaces %} secrets
 {% data reusables.enterprise-migration-tool.data-not-migrated %}
-* User access to the repository
 
 When you migrate a repository directly, teams and team access to repositories are not migrated.
 

data/reusables/enterprise-migration-tool/data-not-migrated.md

@@ -1,5 +1,6 @@
 * Audit logs
 * {% data variables.product.prodname_code_scanning_caps %} results
+* {% data variables.product.prodname_codespaces %} secrets
 * Commit status checks
 * {% data variables.product.prodname_dependabot %} alerts
 * {% data variables.product.prodname_dependabot %} secrets
@@ -21,6 +22,8 @@
 * Repository stars
 * Repository watchers
 * Rulesets
+* Sub-issues (see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/about-issues#about-sub-issues))
 * Tag protection rules
+* User access to the repository
 * Users' profiles, SSH keys, signing keys, or {% data variables.product.pat_generic_plural %}
 * Webhook secrets