We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1792

JCMA Should validate the pkey with special characters during migration

    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary: At present, the Java Cloud Migration Assistant (JCMA) does not present any warning or error messages during the data preparation phase, even when a pkey of the project contains special characters. 

      As pkeys with special characters are not supported in the cloud, this could potentially lead to issues after the migration project has been completed. 

      It would be beneficial to implement a validation system that displays warning or error messages during the data preparation stage “if any pkeys not conforming the pkey format definition in the cloud”

       

      Replication Steps: 

      • Create a project in the Jira server
      • Modiy the pkey value to include '_' in both project and project_key tables.
      • Migrate newly created project to cloud using JCMA (Make sure the pkey is reflecting properly on the UI)Not

      Note:  As the latest Jira version doesn't allow creation of a pkey with special characters, pkey was changed from the DB.

      Actual Result:

      • Project migrates successfully to the cloud without any warnings/errors.

      Expected Result:

      • JCMA should not allow the migration of such projects as the pkey format with special characters is not supported in the cloud.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Migration Platform'
            1. Migration Platform
            2. MIG-1792

            JCMA Should validate the pkey with special characters during migration

              • 2
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                Summary: At present, the Java Cloud Migration Assistant (JCMA) does not present any warning or error messages during the data preparation phase, even when a pkey of the project contains special characters. 

                As pkeys with special characters are not supported in the cloud, this could potentially lead to issues after the migration project has been completed. 

                It would be beneficial to implement a validation system that displays warning or error messages during the data preparation stage “if any pkeys not conforming the pkey format definition in the cloud”

                 

                Replication Steps: 

                • Create a project in the Jira server
                • Modiy the pkey value to include '_' in both project and project_key tables.
                • Migrate newly created project to cloud using JCMA (Make sure the pkey is reflecting properly on the UI)Not

                Note:  As the latest Jira version doesn't allow creation of a pkey with special characters, pkey was changed from the DB.

                Actual Result:

                • Project migrates successfully to the cloud without any warnings/errors.

                Expected Result:

                • JCMA should not allow the migration of such projects as the pkey format with special characters is not supported in the cloud.

                        Unassigned Unassigned
                        61223e4382b7 Prasanth K P
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            61223e4382b7 Prasanth K P
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated: