Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11874

When migrating Jira Cloud to Cloud, boards with missing filters are identified in pre-checks, but there is no way to delete them

    • 50
    • 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.

    • Jira Software, Jira Service Management

      Issue Summary

      When performing a Jira cloud-to-cloud migration, the pre-checks will identify affected boards (based on Board Location) with references to invalid filters, resulting in a log like this:

      Project Id,Project Name,Board Id,Board Name,Invalid Filter id
      12345,Project Name,120,Example Board Name,40543

      However, because the board is not accessible due to the invalid filter, it cannot be accessed for deletion or correction. This results in the migration being blocked.

      This is reproducible on Data Center: (no)
      Jira Cloud currently prevents you from deleting a filter that is currently associated with a board. Reproducing this problem would require manual intervention via the database.

      Steps to Reproduce

      1. Create a board and set the Location to a project that you will migrate from cloud-to-cloud.
      2. Manually invalidate the board by setting the associated filter to an invalid filter ID via the database.
      3. Attempt to migrate the project from cloud-to-cloud.

      Expected Results

      The precheck would provide a path to mitigate the boards that are blocking the migration. Some suggestions:

      • An option to delete the offending board
      • An option to update the offending board
      • An option to clear the Location field for the offending board

      Actual Results

      A log file is provided with the offending board. Atlassian Support must be engaged to remediate the boards.

      Workaround

      Contact Atlassian Support.

            [CLOUD-11874] When migrating Jira Cloud to Cloud, boards with missing filters are identified in pre-checks, but there is no way to delete them

            Dohyeong Kim added a comment - https://getsupport.atlassian.com/browse/MOVE-1777390

            Julien MALLARD added a comment - - edited

            Hi,

            As a workaround, I was in a hurry and I was able to delete the broken boards via API. They were invisible/unusable anyway...
            https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-delete

            Note : I used curl with basic authentication since I was not able to use a bearer token like in the example.

            Another note, if you wonder : support informed me "that currently there is no such API to update the filters"

            Julien MALLARD added a comment - - edited Hi, As a workaround, I was in a hurry and I was able to delete the broken boards via API . They were invisible/unusable anyway... https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-delete Note : I used curl with basic authentication since I was not able to use a bearer token like in the example. Another note, if you wonder : support informed me "that currently there is no such API to update the filters"

            It would be great to have either automatic board validator/fixer process in background or an option to skip all invalid boards like it is implemented in JCMA for boards with invalid owners.

            Oleksiy Brushkovskyy (atla) added a comment - It would be great to have either automatic board validator/fixer process in background or an option to skip all invalid boards like it is implemented in JCMA for boards with invalid owners.

              Unassigned Unassigned
              33b51f2467cc Ahmed Raafat
              Votes:
              3 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: