thank you for your video, but do you know if it is possible to generate a full export file directly integrated workflows, users, permissions et data of course. If it not exists, how works the migration to the Clould Altalssian. I hope your anwser
Thank you for the walk through. Is there more detail on the fields to map. For instance, should I map issue id and issue key as my new project has a different issue key
Hi, in general, you need to map all the fields on which you have values: the epics, labels, custom fields (comments), priority, description, issue type, story points, due dates, estimates, etc. Check-in your CSV all the fields that have value, those should be the ones mapped. The fields that have an ID will change issue ID, sprint, assignee.
Thanks for the the reply. The file I uploaded had 173 issues and different errors for different issues. For example my import consists of users who are not working in the project any more. So, few issues are getting uploaded and rest are highlighted in yellow and red color warning signs.
@@mohammedamer1967 I see. Are these tickets up to date? If yes, then you can ignore the users, they aren't carried over anyways. However, did you try to import it even with the errors? It will be good to have a list of the errors. Can you share that in a generic way - like the users who aren't in the project anymore. And I can help you better. Ideally they'll be fixed before importing so you are sure all the info you care about is imported correctly.
Thank you for the follow up. Detailed explanation : Total issues 3111. As per your instructions I divided them equally in 3 sheets. Wanted to start import with 100 issues for testing purposes. Did the import in both ways - All types together and only epics. But faced errors in both the cases. I would have send you the screenshots but youtube comments does not have that option. Thanks.
Hi....I was able to upload all 3000+ issues in one go. A person with Jira Admin global rights will be able to do it. But we had to skip the users from the previous Jira board. Thanks for the video though :)
Hello, Thank you for your explanations. I have a trouble about "Map fields" 1. If I need to match all fields, some of them, I could not find it. For example : Watchers ID? I'm clicking on this field and no match as same as Watchers ID Also on my excel file is written watchers ID, How can I match them. 2. I tried to match them just like fun. (just wanted to move next step) but I can't go on next step! I stucked at 12:45 exporting Epics 3. Do I need to convert, what do I downloaded (Csv file)? 4. Also do I need to create new project and build issue types, workflows etc? Before migration?
Thank you for the greatVideo ! One question ... what about the attachments inside of the Jira Issues ? Is there also a way to migrate data without a plugin ?
Unfortunately those you lose them. Ideally you can go in ticket and save them to a google drive for example and then add a link to then which will be carried over.
Hi, Thanks for video but your method to import Sub-task is wrong and does not work in the way you have. Normally importing sub task using excel never works when I look at different tutorials in Jira community. So please either remove that piece from your video or provide steps in details which you have skipped from the mappings till end.
You know what I think I found an easiest way to do it. Import all the issue types including Sub-Types as well, go to the new site where you have imported the data and using Bulk Change option from Advance Search - select sub task - select the action Move issues - select the Parent Issue - click Next That’s it and it is done but the down side it works for less number of task and if you have more then it may not be helpful 🙂
Great walk through
👍
thank you for your video, but do you know if it is possible to generate a full export file directly integrated workflows, users, permissions et data of course. If it not exists, how works the migration to the Clould Altalssian. I hope your anwser
Thank you for the walk through. Is there more detail on the fields to map. For instance, should I map issue id and issue key as my new project has a different issue key
Hi, in general, you need to map all the fields on which you have values: the epics, labels, custom fields (comments), priority, description, issue type, story points, due dates, estimates, etc. Check-in your CSV all the fields that have value, those should be the ones mapped.
The fields that have an ID will change issue ID, sprint, assignee.
How to export request type?
Hey . Keep up the awesome work! Do you plan to make more Video on Jira Project Management? Kind regards, Deepak
Sure. What topics are you interested in?
Hi...great video.....I was able follow your process but the problem is I'm having lot many errors when Im importing
hey, thanks!
what kind of errors do you have on import? So I can see how you could fix them.
Thanks for the the reply.
The file I uploaded had 173 issues and different errors for different issues. For example my import consists of users who are not working in the project any more.
So, few issues are getting uploaded and rest are highlighted in yellow and red color warning signs.
@@mohammedamer1967 I see.
Are these tickets up to date? If yes, then you can ignore the users, they aren't carried over anyways.
However, did you try to import it even with the errors? It will be good to have a list of the errors. Can you share that in a generic way - like the users who aren't in the project anymore. And I can help you better.
Ideally they'll be fixed before importing so you are sure all the info you care about is imported correctly.
Thank you for the follow up.
Detailed explanation :
Total issues 3111. As per your instructions I divided them equally in 3 sheets.
Wanted to start import with 100 issues for testing purposes. Did the import in both ways - All types together and only epics. But faced errors in both the cases.
I would have send you the screenshots but youtube comments does not have that option. Thanks.
Hi....I was able to upload all 3000+ issues in one go.
A person with Jira Admin global rights will be able to do it. But we had to skip the users from the previous Jira board. Thanks for the video though :)
Too much talking. Video actually begins at 2:00. 2 minutes into the video!
Hello,
Thank you for your explanations.
I have a trouble about "Map fields"
1. If I need to match all fields, some of them, I could not find it.
For example : Watchers ID? I'm clicking on this field and no match as same as Watchers ID
Also on my excel file is written watchers ID,
How can I match them.
2. I tried to match them just like fun. (just wanted to move next step) but I can't go on next step!
I stucked at 12:45 exporting Epics
3. Do I need to convert, what do I downloaded (Csv file)?
4. Also do I need to create new project and build issue types, workflows etc? Before migration?
Hello what is your contact info for mentoring program
Thank you for the greatVideo ! One question ... what about the attachments inside of the Jira Issues ? Is there also a way to migrate data without a plugin ?
Unfortunately those you lose them. Ideally you can go in ticket and save them to a google drive for example and then add a link to then which will be carried over.
Thanks for the video! How about Migrating the Agile Reports?
Hi, Thanks for video but your method to import Sub-task is wrong and does not work in the way you have. Normally importing sub task using excel never works when I look at different tutorials in Jira community. So please either remove that piece from your video or provide steps in details which you have skipped from the mappings till end.
You know what I think I found an easiest way to do it. Import all the issue types including Sub-Types as well, go to the new site where you have imported the data and using Bulk Change option from Advance Search - select sub task - select the action Move issues - select the Parent Issue - click Next
That’s it and it is done but the down side it works for less number of task and if you have more then it may not be helpful 🙂
Great tutorial, thank you