We have mutliple projects, each project may have different Issue Types and different custom fields. Is there a way I can move an issue from one project to another without losing any data?
in order to move the issues you can do what Lucas and Pedro have mentioned, but if your destination project has different custom fields than your source project you will loose their value (in case they were filled in). When you have different workflows with different statuses these will also be (re-)set to a new status. The move process will suggest the new statuses for you to choose the correlation between the different workflows.
In order not to loose the custom field values you have to have the same custom fields in both projects. If you don't want to see these custom fields in the destination project then make sure you don't include them in the edit/view/new screens for the different workflows you have in your destination project.
Depending on how your custom fields are configured (overall scope, only certain issue types, configuration schemes...) you might need to adjust the settings so that they're valid in all projects among which you wish move your issues.
hope this helps,
You can use the Bulk Move (https://confluence.atlassian.com/display/JIRA/Modifying+Multiple+('Bulk')+Issues) to move issues from one project to another. But if you don't want to loose data stored in the custom fields, you need to have these fields also mapped to the destination project.
The way moving issues from one project to another project is a trivial task on the desktop platform.
How can this same operation can be accomplished from the iOS jira application .
i trying navigating through all the possible flows, and the left slide from the backlog view has a move option but the action only provides move to top and move to bottom.
i feel this is an important feature that is missing in the app, or if it’s there it’s isn’t easily discovered.
can someone shed some light?
I am facing the same problem while moving issues from one project to other, the assignee of the former issue remains the same for the moved issue .One workaround is by using Jira lite automation plugin pro version,but it encures additional cost .
Kindly suggest some other fix.
Regarding your statement below, how do you map custom fields from one project to another project.
I have a project with custom field "Steps to reproduce". I want to map it to "Description" field in the destination project when doing Bulk Update.
"But if you don't want to loose data stored in the custom fields, you need to have these fields also mapped to the destination project."
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events