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-1918

Sprint deleted in server/DC should have the historical data migrated to avoid inconsistent reports in Cloud

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

      Problem Definition

      In server, if you add an issue to Sprint A -> Move to Sprint B -> Move to Sprint C
      Then you delete Sprint B

      Now, when you migrate to the cloud, there will be no historical data from that issue moving from A to B.
      So, the Sprint Report in the cloud will show that issue in Sprint A and Sprint C (only the reports, not the real sprints), where it should be showing only in the Sprint C report.

      Suggested Solution

      Those historical data are preserved in the server even if the Sprint is deleted.
      This data needs to be migrated in order to generate accurate reports.

      Why this is important

      This issue creates inconsistent data in the reports, and they could lose their credibility because of that.

      Current Workarounds

      There is no workaround at this point.

            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-1918

            Sprint deleted in server/DC should have the historical data migrated to avoid inconsistent reports in Cloud

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

                Problem Definition

                In server, if you add an issue to Sprint A -> Move to Sprint B -> Move to Sprint C
                Then you delete Sprint B

                Now, when you migrate to the cloud, there will be no historical data from that issue moving from A to B.
                So, the Sprint Report in the cloud will show that issue in Sprint A and Sprint C (only the reports, not the real sprints), where it should be showing only in the Sprint C report.

                Suggested Solution

                Those historical data are preserved in the server even if the Sprint is deleted.
                This data needs to be migrated in order to generate accurate reports.

                Why this is important

                This issue creates inconsistent data in the reports, and they could lose their credibility because of that.

                Current Workarounds

                There is no workaround at this point.

                        Unassigned Unassigned
                        dc480d41705f Josteir Cunha
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            dc480d41705f Josteir Cunha
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated: