Currently, when needing to migrate only 1 SFM change and there are multiple SFM's under that specific SFW (wizard) ALL SFM's get migrated.
In my specific situation I had made a change to 1 SFM in SBOX that needed to be migrated to PROD right away. Meanwhile, in SBOX I had other SFM's in development that I didn't want to migrate just yet. I had only selected the 1 changed SFM for migration and it was the only one that appears in the list "to be migrated".
However, once the migration completed users started to notice things were different. It was only then that I realized that ALL SFM's related to a single SFW was migrated over to PROD which yielded undesired results.
If one SFM is selected then only one should be migrated. You may not always need or want to migrate all SFM's under a single SFW.
What is the underlying problem do you intend to solve with this idea?
Trying to eliminate PROD errors by having control of what SFM's are selected for migration, regardless of the SFW grouping.
How is the problem being addressed today, if at all?
Having to address the unwanted migrated SFM's in PROD after errors are created as a result of an non-changed/dev changed SFM being migrated as the a default setting due to the relationship with the SFW.