Deployments page does not load after migrating using JCMA and performing a deployment to a migrated issue ticket

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      After migrating Jira Server/DataCenter to Jira Cloud using the JCMA tool, linking Jira Cloud to Bitbucket Cloud, and performing a deployment on Bitbucket linking to a Jira issue that was migrated, the deployment information is correctly detected by Jira on the Development Panel on the issue, but the deployment is not showing on the Deployments page, where only the onboarding page with the message  "You're almost ready to view deployments in Jira" is displayed

      Steps to Reproduce

      1. Migrate Jira Server/Datacenter to Jira Cloud using JCMA
      2. Link Jira Cloud and Bitbucket Cloud instances
      3. Execute a deployment on Bitbucket that references a jira issue that was migrated (it can contain the issue key in the commit message or branch name)
      4. Access the Jira issue and verify the deployment information is correctly detected by Jira on the Development Panel on the issue 
      5. However, when trying to access the Deployments page to see all deployments in the project, the onboarding page is shown with the message You're almost ready to view deployments in Jira" even though the deployment already happened :

      Expected Results

      The Deployments view should open with the information of the deployments that already happened and which information was already correctly detected by Jira on the Development Panel on the issue.

      Actual Results

      The Deployments page keeps showing the onboarding page as if some validation is still missing.

      Workaround

      To workaround this issue and make the Deployments view to load the deployments you can follow the below steps : 

      1. Create a new issue in the Jira project
      2. Execute a deployment on Bitbucket linking to this new issue (not a migrated issue)
      3. After the deployment is complete, navigate to Jira and the Deployments view page should correctly detect the deployment, including the previous deployments made to the migrated issues that were not showing. 

        1. image-2023-09-05-17-56-56-839.png
          122 kB
          Patrik S
        2. image-2023-09-05-18-01-12-844.png
          555 kB
          Patrik S

            Assignee:
            Unassigned
            Reporter:
            Patrik S (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: