Automation rule - trigger is version released - create task in another project, link to release

[Claire Riquelme]

I have created an automation rule that creates a task in another project when a version is released.  The task created needs to have a specific component set and link to the release.

The task is being created, the component is set, but I can't find a way to include a link to the release.  Please let me know if this is possible.

[Trudy Claspill]

Hello @Claire Riquelme 

Welcome to the Atlassian community.

Releases are project specific. If the Release is in Project A and you are creating the issue in Project B, then you will not be able to associate the issue created in Project B to a Release in Project A.

Apart from that, the way to "link" an issue to a Release is to set the Fix Versions field for the issue to the specified release.

[Claire Riquelme]

Thanks for the quick response.  I'd be happy using fixed version, and I did try to set the fixed version in the Project B, but it didn't work.  Can you please step me through how to add the release to fixed version via automation?

[Piyush Annadate _ACE Pune_]

Hello @Claire Riquelme ,
Welcome to the Community !
Actually, the release version are project specific and cannot have cross project issues/work items reference. Hence, you cannot have an release version across project.

You may add a label for the release version name; else you can create a readonly release version name fields that would again the name of the release version populated. 

Again, for the above, you will not be able to get another project issues into the release version report/list.