Bug #5987

Shared library migration does not check if the libraries are linked to the model properly

Added by Janne Kauttio over 2 years ago. Updated about 1 year ago.

Status:On holdStart date:
Priority:4Due date:
Assignee:Antti Villberg% Done:

0%

Category:-Spent time:-
Target version:-
Release notes:
Story points-
Velocity based estimate-

Description

1. Start with a shared library L (Version A) and a model M which uses definitions from L
2. Create a new version of L (Version B) from the context menu (and make some changes)
3. Migrate from A to B with the migration wizard from the context menu
4. Delete L (Version B) (does not produce any warnings even though all instances based on the shared library are removed from M)

The problem is that the step 3 does not check that the new library version is linked properly with the model. The instances from A are (apparently) replaced correctly with instances from B, but as there is no link between the model and B the deletion of B can not see that it is actually in use.

History

#1 Updated by Tuukka Lehtonen over 2 years ago

  • Release set to 25

#2 Updated by Tuukka Lehtonen about 2 years ago

  • Target version changed from 1.19.0 to 1.20.0
  • Release changed from 25 to 29

#3 Updated by Tuukka Lehtonen about 2 years ago

  • Due date deleted (2015-08-14)
  • Target version deleted (1.20.0)
  • Start date deleted (2015-08-13)
  • Release changed from 29 to 31

#4 Updated by Tuukka Lehtonen over 1 year ago

  • Release changed from 31 to 39

#5 Updated by Tuukka Lehtonen about 1 year ago

  • Release deleted (39)

#6 Updated by Tuukka Lehtonen about 1 year ago

  • Status changed from New to On hold

Also available in: Atom PDF