Hi @aamelyan - Releases are specific to each project so you need to recreate the desired releases in the target project and release/archive accordingly. Once you've done that, you can move your issues and it will retain the Fix/Affects version fields.
Well, I was looking for the same functionality that we have for issues where you move the release form one project to another. I also found question, but I yet to hear how this works using the add-on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In scenarios where I have multiple projects that need to share the same release structure, I have gone this route:
RULE #1 Version Created
Labels IN (RELEASE)
{{version.name}}
{{version.releaseDate}}
RULE #2 Version Released
Labels IN (RELEASE)
{{version.name}}
{{version.releaseDate}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.