-
Suggestion
-
Resolution: Unresolved
-
None
-
10
-
Issue Summary
This is reproducible on Data Center: (yes) / (no) : Yes
Steps to Reproduce
- Migrate an open sprint to the cloud.
- Change the status of sprint in cloud to `Closed` without making any change in server data.
- Migrate the sprint again as part of dashboards/cross project boards migration.
Current Behaviour
The cloud data is overwritten by server data upon re-migration.
Proposed Results
Customers should be able to choose which data to keep when the data on server and cloud for Sprint entity is different.
Workaround
Workaround has been defined as part of https://jira.atlassian.com/browse/MIG-1925
- resolves
-
MIG-1925 JCMA reopens closed Sprints in Server to Cloud migration
-
- Closed
-
- has action
-
SETM-367 Failed to load
- links to
- relates to
-
MOVE-1775081 Loading...
Provide a way to chose between server and cloud data for sprint across multiple migrations (Config Drift)
-
Suggestion
-
Resolution: Unresolved
-
None
-
10
-
Issue Summary
This is reproducible on Data Center: (yes) / (no) : Yes
Steps to Reproduce
- Migrate an open sprint to the cloud.
- Change the status of sprint in cloud to `Closed` without making any change in server data.
- Migrate the sprint again as part of dashboards/cross project boards migration.
Current Behaviour
The cloud data is overwritten by server data upon re-migration.
Proposed Results
Customers should be able to choose which data to keep when the data on server and cloud for Sprint entity is different.
Workaround
Workaround has been defined as part of https://jira.atlassian.com/browse/MIG-1925
- resolves
-
MIG-1925 JCMA reopens closed Sprints in Server to Cloud migration
-
- Closed
-
- has action
-
SETM-367 Loading...
- links to
- relates to
-
MOVE-1775081 Loading...