- MIG-1851Migration of AR Shared Teams adds unexpected user to all Shared Teams
- MIG-1850Migrate All at Once should migrate Archived Issues
- MIG-1849CCMA Group Page restrictions are dropped with scoped user/group migration if the group does not have space permissions
- MIG-1848JCMA 1.11.0 fails to load without Jira Software
- MIG-1847Support for custom emojis/emoticons in CCMA
- MIG-1845CMAs should provide a clear warning when blocked by IP Allowlisting
- MIG-1844Make the "Something went wrong" error more descriptive
- MIG-1843None Selection Mode in Cross Projects Boards and Filters
- MIG-1842Migrating a project using JCMA results in DynamoDbException
- MIG-1841Migration from Server to Cloud might bring orphan custom field options which cause difficulties with the issue view and issue search
- MIG-1840Enhance BCMA Migrations with Progress Tracking and Monitoring
- MIG-1839Migrate app custom field types
- MIG-1838Preflight cache is not invalidated when a new invalid/duplicated user votes or watches an issue
- MIG-1837We couldn't export Custom Field Default Value XXX. Reason: java.lang.Exception: This export context type does not support project (CrossProjectDataExportContext). [JCMA 000]
- MIG-1836Non-existent issuetypes are present in the Jira Cloud instance after migration via JCMA
- MIG-1835JCMA - Make the "we can't communicate with your server" error more descriptive
- MIG-1834JCMA Preflights: Precheck for JSM present in cloud is misleading
- MIG-1833Migration of dashboard shows successful despite missing dependancies
- MIG-1832"Assess your apps" section is missing from CCMA UI when unexpected error occurs
- MIG-1830Creating a CCMA migration plan through the REST API can cause the SpaceKeysConflict pre-flight check to PASS when it should FAIL.
- MIG-1829Add ability for Jira Cloud Migration Assistant to migrate attachments after project migration
- MIG-1828JCMA cloud token can't be renewed when the authentication has expired for the Prepare Your App page.
- MIG-1827LMS skips Display links with unexpected characters in the spacekey
- MIG-1823Fix links to page drafts in Jira and Confluence
- MIG-1821Configuration only migration for Jira - server to cloud, JCMA
- MIG-1820Migrating apps data via the “Migrate all data at once” pathway duplicates custom fields in Jira Cloud.
- MIG-1819Product link fixing can't fix URLs that contain JIRA filter entities with IDs
- MIG-1818Bitbucket Cloud slug character limit impacts ability to migrate to cloud
- MIG-1815The migration error for issue security level should be more clear
- MIG-1813Jira issue history is not properly transformed during migration
- MIG-1811Incorrect user and group count on JCMA migration plan
- MIG-1809JCMA doesn't include the details of archived users (ArchivedBy) in the migration export.
- MIG-1808Product links fixing UI does not support fixing links in products that have been in Cloud from the beginning
- MIG-1807Enable admins to update product links in case of Migrate all at once
- MIG-1806Team Calendar Who field not migrated for MYSQL
- MIG-1805BCMA version history does not provide historical version release notes
- MIG-1804Server to Cloud migration changes all date field values of jira issues when migrated to different time zone
- MIG-1803Customers are not getting created as portal-only customers on cloud when Confluence migration is initiated before jira
- MIG-1802Give users the option to opt out of the "Migrated on..." text added while using Copy product data from cloud to cloud
- MIG-1801Migrating a project having special characters(_) in the pkey to Jira Cloud succeeds without warnings
- MIG-1800Migrating with JCMA will update Sprint Start Date with the Activation Date
- MIG-1797Interrupting a CCMA plan to add users to a group, then resuming plan, migration will not reflect the last change
- MIG-1795When using Migrate All At Once and Exclude Attachments, the attachments references should also be excluded
- MIG-1794Custom field Customer Request Type is not migrated with JCMA and may cause JQLs to break
- MIG-1793Product Link Fixing doesn't support federated migrations
- MIG-1792JCMA Should validate the pkey with special characters during migration
- MIG-1791Test MIG for version update
- MIG-1789Provide Confluence server and Confluence cloud content mappings after migration
- MIG-1788CMAs should provide breakdown of user accounts and licensing
- MIG-1787App assessment on DC shows misguiding information on the migration path
363 of 1664