Sorry, but I doubt that this feedback process in the case is really exsiting. At least from the past the original case was NOT updated once the fix was out. And also, the suppoer answer that I gave you as an example does not fit to your statement - why I should I monitor the CQ-number although I get notified via an update of the case? So, I would really appreciate to check to process. Is it is like you said, that there is already a process that the connected case get's updated, then that's perfe...

Yes, but that's not the point. From my ticket I get such unswers "... I would request you to please monitor the CQ-4298048 inclusion of the fix for your issue on the future release notes of the coming versions or service packs/CFPs on our official online documentation/ release document. " And here, I would like to have an automated notification in order not to check the release not for my several CQ-number bugs.

Hi,we have also raised a support ticket to get an answer how to break inheritance on field level within the component. Re: Field Level Inheritance - MSM For Classic UI (AEM 6.1) it seems there is a "hidden" property but I don't know about touch UI so far.From Business perspective breaking the inheritance on component level only, with having all fields cancelled at once, does NOT match the real live requirements of multilanguage websites for large company with hundreds of websites...

Hi,I having the same challenge: I need a field level based inheritance of a component since I need to avoid cancelling the whole component inheritance and therefore all fields.I found the property "fieldEditLockMode" in this article: aem - CQ5 - Cancel individual property inheritance of a Live Copy component - Stack Overflow. Adding this to the component dialog let the small locks appear in front of the field in the dialog. But when I cancel the inheritance of a field, changing the content, clos...

Thanks, well an inplace upgrade is possible, of course. Our consideration was that since we did always inplace upgrade starting with CQ 5.4, it might be a good idea to start from scratch and maybe leave old stuff from older versions that is not in use anymore behind us...

Hi,we are also planning to migrate from AEM 6.1 SP1 to AEM 6.3. We are thinking of setting up fresh AEM 6.3 and migrate content then. But we have the need to keep and migrate the versions. Is this possible? Does anyone have experience with this scenario?Thx