The FAQ includes this mention:
### Will the Migration API support all my import needs?
Yes, the API can do everything Import/Export could, including support for integration fields, legacy slices, and localized content.
However, I checked the documentation but could not see any reference to it. The Migration API seems to have lost the ability to set release name? Sorry if I missed it.
In our organization, one or more documents can be updated/localized/modified in the context of a project.
Until now, the import tool was handling it well because we would set the release name with a context information (e.g. JIRA ticket ID), so anyone jumping in Releases would easily understand what a particular release is about, e.g. and would know when to publish it. Why is this not supported? If it is, how to do it?
Needless to say, without it, it will be quite a mess to keep our release process clean and efficient.
Please help.