Word doc re upload option not updating sub assets folder

[#1]

Request for Feature Enhancement (RFE) Summary:	Word doc re upload option not updating sub assets folder
Use-case:	When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder. This is a priority issue and we need to resolve on urgent. Could you please check and let us know on this issue. 1. Navigate to Assets console, files option 2. Upload a document with some images. update metadata. 3. Change the images/remove one or two images in the word document. 4. Upload word document with Create Version option 5. Check the sub assets folder , observe mismatch with source word document .
Current/Experienced Behavior:	When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder. 6.5.22, 6.5.20, and 6.5.18, and the behavior is consistent across all of them.
Improved/Expected Behavior:	When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder.Sub assets folder need to be updated even with create version option .
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM 6.5 SP20 6.5.22, 6.5.20, and 6.5.18, and the behavior is consistent across all of them.
Customer-name/Organization name:	CISCO
Screenshot (if applicable):
Code package (if applicable):

[#2]

@abomma Thanks for proposing this idea. This has been reported to the engineering under the internal reference ASSETS-56545. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.