Component level inheritance status in the AEM language Master rollout page

[#1]

Request for Feature Enhancement (RFE) Summary:	Enable Component level inheritance status OOTB without the need to overlay
Use-case:	As a content author, MSM roll-outs is a key content authoring activity. When a content author performs a roll-out of the content from the language master to the related livecopies, there is a provision to see the page level inheritance status in the rolloutdialog.html. But this page doesn't provide any information about the component level inheritance status of all the components inside the live-copy page. At times, this creates a lot of confusion where a content author is trying to roll-out a page to live copy but some components are not getting updated due to the fact that component inheritance is broken on the live-copy page. if there are too many components on the page, then it becomes very tedious process for the content author to check each and  every component for its inheritance status. Currently, this can be solved by overlaying the livecopies.jsp (/libs/wcm/msm/components/touch-ui/livecopies/livecopies.jsp) and adding the required code but It would be great if this can be made available OOTB.
Current/Experienced Behavior:	RolloutDialog.html shows only page level inheritance status
Improved/Expected Behavior:	RolloutDialog.html should show another column to display the component level inheritance status
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as cloud service - SEP 2023 SDK
Customer-name/Organization name:	NA
Screenshot (if applicable):	By overlaying the livecopies.jsp, we can add another column and for each of the livecopy pages, we can look through  all the components and see if atleast one of them has a cq:livsyncCancelled mixin added and based on that we update the status in the above table.
Code package (if applicable):

[#2]

@kautuk_sahni , while this is something that can be done by overlaying the relevant jsp and customizing it, I would like to check if making this available OOTB makes sense. Please let me know. Thanks.

[#3]

@Harwinder-singh Thank you for sharing this. We review the Ideas pool every 2 weeks as of now. I'll review these soon. I'll keep you posted about this.

[#4]

@Harwinder-singh 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-17820. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#5]

@Harwinder-singh acknowledged this as a fair request. Could become complex though depending on the number of components on a page.

[#6]

@kautuk_sahni , Thanks. Is there any timeline by which we should expect this to be part of a feature activation ?

[#7]

@Harwinder-singh, I will keep you posted with the update.