Bulk moving issues to another project lose all data

Question

Hi,

I've seen discusion on that topic, but not sure in which release it is planned to be solved.

When I move issues from one to another project all data in terms of releases are list nevertheless that I choose within the bulk process to retain them.

This is essentially needed, otherwise all information about releases are lost.

Thank you.

Best,

John Funk · Answer

Yes, but the only manual part is simply creating the new release in the project you are moving to. That should be pretty quick for you.  ;-)

I could not find any open tickets that Atlassian is planning on putting this functionality in a new version.  :-(

It this answers your question for you, can you click on the Accept Answer button above to close this one out? Thanks!

neli.trosic · Answer

Thank you @John Funk for the suggestion. It is ok, but still require a lot of manual work, which I'd like to avoid 😎 if it's possible of course

John Funk · Answer

Hi Neli - Welcome to the Atlassian Community!

It's probably just that the bulk change option is not allowing you to keep the release/fix version right now. Not sure what the current single move is actually doing right off the top of my head, but I would suspect it is creating a new entry in your project for the release first, then allowing you to copy the value over.

So, as a workaround, I would create the release in the new project with the EXACT same name as the one you are moving from. That way when you do a move, it should copy the value over.