Update an existing email Fragment from a imported package - Status changed to: Investigating

[#1]

It is important to us that, when you import a package with changes to existing email Fragments the existing Fragment can be updated not just imported. When you use Fragments in many templates it become a problem when the Newley imported fragment comes in as a new "file with a new id" the templates using the old existing fragment is not been updated with the new version. This most be done manually template by template where the fragments is used - and change the old one to the new one. We hope that this can be automated when importing a fragment you can choose is this new one should update a old one - and witch. 

Even better is you also can do multiple selection where it is the same process for many segments.  

[#2]

I agree! My client, Vanguard is also using this feature for importing fragments from UAT to Prod and it is very confusing when using the 'create new' option allows to fragments to exist with the same name. What happens if both are published? Is that possible? 
I agree there needs to be an option to 'overwrite existing'. Or at least give an error or a warning if you try to publish a draft fragment from a recent import that has a same name as an existing fragment what the implications are.

[#3]

@Selliers  @SamanthaBr3  please feel free to submit an enhancement request for this. 

[#4]

Really appreciate that you are looking into this.