Merge parts functionality fails to preserve copy_part mapping
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.7 |
Fix Released
|
Undecided
|
Unassigned | ||
2.8 |
Fix Released
|
Undecided
|
Unassigned | ||
2.9 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The Merge Monograph Parts functionality new in 2.7 does not preserve the copy/part mapping for the deleted part.
Here's the original launchpad bug:
https:/
and the commit:
http://
When selected parts are merged in the Manage Parts interface in the client, the user chooses a "prevailing item", which is the part to be preserved. The remaining selected parts are deleted when the user clicks to choose the prevailing item.
Any copy that was mapped to the deleted parts, loses its part mapping rather than having the mapping updated to the prevailing part.
It looks like a row is being deleted from asset.copy_part_map rather than being updated with the prevailing part's id.
Updating this mapping is essential to using this functionality.
description: | updated |
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
assignee: | Galen Charlton (gmc) → nobody |
Changed in evergreen: | |
assignee: | nobody → Dan Wells (dbw2) |
Changed in evergreen: | |
milestone: | 2.next → 2.10-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Yes, we've seen this happen, too. I've been pointing the item to the desired part prior to merging the parts, just to avoid running into the deletion.