Since we are right now in the process of refactoring the entire storage subsystem of YaST, we will postpone this for the new implementation. We will watch out that this will not happen in the new one, too. But I don't think we can spare the resources to fix this pretty complex scenario in the old code as well. So we will have to ask for your patience for the fix in the great, shiny new storage-ng.