Hi Yuggi,
There is a way how to link Change Request to a Release via Parent field on Change Request. You can configure Related Lists on Release table to add "Change Requests > Parent" related list so that you see all changes related to one Release and you can configure Change Request form to add Parent field to the form (it is not there by default). See my screenshots after I did these configurations.
Release form:
Change Request form:
From what I saw existing implementations of Release Management with connection to Change Management, customers usually created custom "Release" reference field on Change Request table. Once you have such field, you can easily link Release to a Change via that field and also add the related list of Changes to Release form.
Additional note - as I have noticed, there is ootb Releases related list on Change Request form. But be careful using that list because the relationship here is made through Parent field of Release record. That means once you link a Release to a Change in that related list, the Parent field will have the value of the Change Request. The issue could be that you have overwritten the original information stored in there which was usually the Product to which the Release is used. So if you use Products and have Release linked to a Product, you will lose that relationship once linked to a Change. See the audit history in my case once I linked a release to a change via that Releases related list:
So the better solution is probably to either use Parent field of Change Request or create a custom reference field.
