Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-83096

Migrating from server to cloud doesn't update the sprint ID in filter JQL

XMLWordPrintable

    • 67
    • 59
    • 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.

      Atlassian Update - September 2024

      Hi everyone,

      Thank you for taking the time to share your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.

      We are actively working on a solution for this feature request. Our team is committed to thoroughly investigating the best way to address this need, and we will keep you informed as we get closer to a possible release date.

      Thank you to every person who provided feedback on this issue. We will update you as soon as we have more concrete information to share. 

      Joe Nguyen
      jnguyen2@atlassian.com
      Product Manage - Jira Cloud

       

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      In cloud:

      1. Create a scrum project PROJA
      2. Create 3 sprints in PROJA containing some sample issues
      3. Now we have at least 3 sprints in the cloud site

      In server:

      1. Create a scrum project PROJB
      2. Create a sprint in PROJB containing some sample issues
      3. Create a filter "Test filter projb" that includes the project PROJB and containing the new sprint
        • The Advanced JQL should look something like "project = PROJB AND Sprint = 3"
      4. Go to the board for PROJB and change the filter to the new filter you created "Test filter projb"
      5. Migrate PROJB to the cloud site using JCMA

      Expected Results

      • The filter "Test filter projb" should include the same Sprint in the cloud as in the server (from PROJB).

      Actual Results

      • Since the Sprint IDs are not updated in the filter JQL during the migration, the filter "Test filter projb" isn't pointing to the same sprint as in the server.
      • The filter is pointing to the sprint that has the same ID in the cloud site (such as a sprint from PROJA) and not the sprint from PROJB.
      • This can also result in broken filters when the sprint ID is not valid in the cloud site.

      No errors are thrown in the log file.

      Workaround

      A manual workaround is to edit the filter in the cloud site to point to the actual sprint.

      If the manual workaround isn't feasible please engage support.

              5ef27d0d5763 Sai Giridhar Pasumarthi
              b352e8382402 Tiffany Cauthen
              Votes:
              15 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated: