Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-137

Export failure when Board's filter has Share-Permission that refers to another Project

XMLWordPrintable

    • 12
    • Severity 3 - Minor
    • 9

      Issue Summary

      If a board's filter has a share-permission that refers to another board then the export will fail with the following unhelpful error:

      Steps to Reproduce

      1. Create a board for a project
      2. Go to the filter used by that project and share it using the Project option
      3. Select another project
      4. Attempt to migrate the project via JCMA

      Expected Results

      The board is migrated correctly and the share permission is retained

      Actual Results

      Project migration fails with this:

      We couldn't export Share Permission XXXX. Reason: java.lang.IllegalStateException: Entity mri:mig:jira/classic:project:XXXX is expected to be exported, but it was not.

       

      Workaround

      Navigate via Jira UI to the board that is failing migrations and remove the shared-permission referencing another project. Attempt to remigrate project. Add the shared-permission when the referenced project is in Cloud.

        1. workaround.png
          workaround.png
          122 kB

            [MIG-137] Export failure when Board's filter has Share-Permission that refers to another Project

            Mark Tunmer added a comment -
            Atlassian Update - November 30, 2023

            Hi Everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base.

            With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time.

            If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue.

            We appreciate your understanding and look forward to providing you with an enhanced migration experience.

            Thank you again for providing valuable feedback!
            The Migrations team

            Mark Tunmer added a comment - Atlassian Update - November 30, 2023 Hi Everyone, Thank you for previously raising this bug and bringing it to our attention. With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base. With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time. If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue. We appreciate your understanding and look forward to providing you with an enhanced migration experience. Thank you again for providing valuable feedback! The Migrations team

              Unassigned Unassigned
              ajean Andy J.
              Affected customers:
              8 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: