Alert: Defect discovered in 3.0.1.3 migration support
A defect has been discovered that prevents 2.x graphical artifacts from migrating properly to 3.0.1.3. At this time, we recommend that you do not perform a migration using the 3.0.1.3 release. If you have already migrated using a prior 3.x release, or you have no need to migrate data from RRC 2.x, then this issue does not affect you. We apologize for any inconvenience, and we anticipate having a fix available here very soon.
|
3 answers
|
The following defect was discovered that prevents 2.x graphical artifacts from migrating properly using 3.0.1.3:
Graphical artifacts (parts, sketches, diagrams) cannot display its contents after migration from 2.x (57322) A hotfix is now available from the All Downloads page with instructions for applying the patch. Note that if you have already migrated using a prior 3.0.1x release, or you have no need to migrate data from RRC 2.x, then the defect does not affect you and you do not need to apply this patch. We apologize for any inconvenience this may have caused. |
Stef
What happens if one goes directly from 2x to 3013 to 40 RC1a, for example. Is there still a need to apply the hotfix or will the 40 upgrade take care of addressing this issue? If not, will the recommendation be to use 3012 or 3014 (if released prior to 40) to migrate from 2x to 40? The following defect was discovered that prevents 2.x graphical artifacts from migrating properly using 3.0.1.3: |
|
Rosa,
The recommendation is to migrate with 3.0.1.3 but apply the hotfix first. If you migrate to 3.0.1.3 without this hotfix and simply proceed on with upgrading to 4.0, your graphical artifacts will still be broken and they can not be repaired post-migration. Hope that helps. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.