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,
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hiii @neli_trosic
This is logical. Cause each release is just for that project and when you move issues from one to another they will be missed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But there is an option in New version in Jira that including releases and fix versions are retained and you have an option to include that info while You're moving issues, so that means that if they will stay writen in backgound codes in Jira also when they are moved to the other project, otherwise I don't see the reason of having that option to choose it or I'm missing something?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.