We do not manage our releases as iterations in Azure Dev Ops - we have a dedicated work item type 'Release' that we associate with all items within a release.
As we use Epics, we currently need our integration to be configured with Epic as the parent. If we attempt to add a 'Linked Item' mapping to the release, this won't work for the Release a Feature/Epic is assigned to on the board, it will ONLY work if you manually go in and add the release in the 'Related Items' tab
We can't track and organise our releases / parking lots of work between Product and the Delivery team - it has to be done manually. Some teams have stopped using Epics as master features and are using them as releases to get round it (which is not ideal for our reporting)
Update the existing Record Links integration function to recognise a feature/epic's parent Release, not just items manually linked in Related Items.