diff --git a/content/en/docs/releasenotes/studio-pro/11/11.12.md b/content/en/docs/releasenotes/studio-pro/11/11.12.md
index 4112a6420c7..7ac4d21c4fb 100644
--- a/content/en/docs/releasenotes/studio-pro/11/11.12.md
+++ b/content/en/docs/releasenotes/studio-pro/11/11.12.md
@@ -39,6 +39,7 @@ weight: 88
 * We fixed an issue where the Java sources of protected modules were added to the Eclipse build path.
 * We fixed an export issue of app-level Maia Agent Skills (*SKILLS.md*) and Agent Instructions (*AGENTS.md*) in solution packages (*.mxsolution*) and regular app packages (*.mpk*).
 * We fixed an issue where the Modernized App Explorer was in a state where the visible nodes and the cursor position were shifted after it scrolled automatically to a position.
+* We fixed an issue where migrating an application could generate incorrect association aliases in View Entity OQL when associations were defined using the OQL COALESCE function. This could result in duplicate column names and validation errors. (Ticket 285886)
 
 ### Known Issues
 
diff --git a/content/en/docs/releasenotes/studio-pro/11/11.15.md b/content/en/docs/releasenotes/studio-pro/11/11.15.md
index 80249e03b19..a2f758107fb 100644
--- a/content/en/docs/releasenotes/studio-pro/11/11.15.md
+++ b/content/en/docs/releasenotes/studio-pro/11/11.15.md
@@ -157,6 +157,7 @@ You can set the default flow shape for all new sequence flows in the **App setti
 * We fixed an issue with `onChange` client actions for [attribute](/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#attribute) and [association](/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#association) widget properties where associated objects passed as arguments to an action were always empty.
 * We now prevent the use of the selection of a widget as an argument for snippet calls, as it is not supported in the client.
 * We fixed a crash that happened when selecting a branch in the App Selector in Studio Pro. This crash occurred when information about the Mendix version was missing from a branch.
+* We fixed an issue where migrating an application could generate incorrect association aliases in View Entity OQL when associations were defined using the OQL COALESCE function. This could result in duplicate column names and validation errors. (Ticket 285886)
 
 ### Breaking Changes