-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Minor
-
-
Jira Software
Issue Summary
The preservation of the order of issue priorities is not maintained, and existing priorities are being altered in the destination site.
Steps to Reproduce
- Configure some priorities (and change the order) in the source site
- Configure some priorities (and change the order) in the destination site
- Migrate using the "Copy Data" feature
Expected Results
The migration should not change existing priorities but add new ones at the end while preserving the source order.
Actual Results
The migration is transferring the existing priorities to the end. The migration does not retain the priorities from the source site.
Workaround
Currently, there is no known workaround for this behavior other than fixing it manually.
A workaround will be added here when available
[CLOUD-12052] The order of issue priorities is not being preserved and existing priorities is changed in the destination site.
Support reference count | Original: 1 | New: 2 |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Support reference count | New: 1 |
Description |
Original:
h3. Issue Summary
The preservation of the order of issue priorities is not maintained, and existing priorities are being altered in the destination site. h3. Steps to Reproduce # Configure some priorities in the source site # Configure some priorities in the destination site # Migrate using the "Copy Data" feature h3. Expected Results The migration should not change existing priorities but add new ones at the end while preserving the source order. h3. Actual Results The migration is transferring the existing priorities to the end. The migration does not retain the priorities from the source site. !image-2024-09-30-09-24-04-157.png|width=439,height=252! h3. Workaround Currently, there is no known workaround for this behavior other than fixing it manually. A workaround will be added here when available |
New:
h3. Issue Summary
The preservation of the order of issue priorities is not maintained, and existing priorities are being altered in the destination site. h3. Steps to Reproduce # Configure some priorities (and change the order) in the source site # Configure some priorities (and change the order) in the destination site # Migrate using the "Copy Data" feature h3. Expected Results The migration should not change existing priorities but add new ones at the end while preserving the source order. h3. Actual Results The migration is transferring the existing priorities to the end. The migration does not retain the priorities from the source site. !image-2024-09-30-09-24-04-157.png|width=439,height=252! h3. Workaround Currently, there is no known workaround for this behavior other than fixing it manually. A workaround will be added here when available |
Affected Products | New: Jira Software [ 18436 ] | |
Component/s | Original: Global Administration - Fields, Issue Types, Screens, Schemes and Priorities [ 66292 ] | |
Component/s | New: Cloud to Cloud Migrations - Jira [ 66501 ] | |
Key | Original: JRACLOUD-84857 | New: CLOUD-12052 |
Project | Original: Jira Platform Cloud [ 18514 ] | New: Atlassian Cloud [ 14613 ] |
Description |
Original:
h3. Issue Summary
This is reproducible on Data Center: yes The preservation of the order of issue priorities is not maintained, and existing priorities are being altered in the destination site. h3. Steps to Reproduce # Configure some priorities in the source site # Configure some priorities in the destination site # Migrate using JCMA h3. Expected Results The migration should not change existing priorities but add new ones at the end while preserving the source order. h3. Actual Results The migration is transferring the existing priorities to the end. The migration does not retain the priorities from the source site. !image-2024-09-30-09-24-04-157.png|width=439,height=252! h3. Workaround Currently, there is no known workaround for this behavior other than fixing it manually. A workaround will be added here when available |
New:
h3. Issue Summary
The preservation of the order of issue priorities is not maintained, and existing priorities are being altered in the destination site. h3. Steps to Reproduce # Configure some priorities in the source site # Configure some priorities in the destination site # Migrate using the "Copy Data" feature h3. Expected Results The migration should not change existing priorities but add new ones at the end while preserving the source order. h3. Actual Results The migration is transferring the existing priorities to the end. The migration does not retain the priorities from the source site. !image-2024-09-30-09-24-04-157.png|width=439,height=252! h3. Workaround Currently, there is no known workaround for this behavior other than fixing it manually. A workaround will be added here when available |
Component/s | Original: Jira - Migrations Platform - JMT [ 63618 ] | |
Component/s | New: Global Administration - Fields, Issue Types, Screens, Schemes and Priorities [ 66292 ] | |
Key | Original: MIG-2043 | New: JRACLOUD-84857 |
Affects Version/s | Original: JCMA - 1.12.6 [ 109697 ] | |
Project | Original: Migration Platform [ 19710 ] | New: Jira Platform Cloud [ 18514 ] |