Good, clear explanation. I solved your "Summary copy / paste to Epic Name manually" problem with an automation: Trigger: Scheduled, set arbitrary time and date (you'll remove / disable this later), check the 'Run a JQL...' box and enter 'issuetype = Epic', and uncheck the 'Only include issues that have changed...' box to make sure you get all epics if you happen to modify one or two while tinkering with the rule. Save the trigger. Then: Edit issue fields, Set Epic Name, copy Summary from Current Issue. Save the action. Double-check that the rule is set to only run in the new company-managed software project. ;) Publish the rule, Run the rule. Disable / remove the rule after spot checking a few Epics to make sure Summary copied successfully to Epic Name field (or check automation rule audit log).

@Flosports-Morgan

3 ай бұрын

Thank you for sharing! I will be working to migrate over 3000 issues, and this is going to help so much!

Thank you for the video! I was trying to read tutorials on how to do this and fried my brain while doing it, but without any success. This was extremely clear and easy to follow, and I got it all done in just a few minutes.

Atlassian has got to know this is an insane amount of work for a common task. Thanks for the pointers. Off I go to create filters.

@ApetechTechTutorials

Жыл бұрын

I 100% agree. This feels like it should be a button somewhere. Or like a click this and that and your done. Shouldn't be this hard.

Liking and subscribing was waaay easier than the migrations I am bound to do :( Thx for the video

Thank you!

Thanks a lot!

Thank you so much

I added a link to your admin playlist in the Atlassian community because of how helpful it is! Hope that’s ok, if you are uncomfortable with that I can remove it!

@ApetechTechTutorials

Жыл бұрын

Totally fine!! Thanks for the support!!

11:38 You can simply use the "Retain" field on the right. All issues will keep the same name and epic.

@qusaiatoon2802

4 ай бұрын

Hello, This is exactly what I was thinking 😅, did you try it with retain? does it actually retain the value? Thanks in advance for you response.

This video is great and is exactly what we are doing, however an issue that comes up that we are looking to solve (and occurs in this video) is keeping the issue key the same (or at least the same number) - so after migrating and deleting the old team-managed project, when you change the new company-managed project to the same project key, the issues have the same issue key. This can mess with a lot of things when the issue key id changes and would love to figure out a workaround or solution.

@ApetechTechTutorials

Жыл бұрын

The only way that I think this would work is if you export all your issues. And then reimport in reverse order (flip them in your csv file).

what about subtasks? I get this warning: Please note that 106 sub-task issues were removed from the selection and do not appear in the table below. You are not allowed to bulk move sub-task issues together with their parent issue. In this case, you will only be asked to move the sub-task if you move the parent issue to a new project.

@Flosports-Morgan

3 ай бұрын

Out of curiousity, did you figure this out? Also, how many issues were you moving?

Thanks for the great video! Does this work for both classic projects and NextGen projects, or only for NextGen projects?

@ApetechTechTutorials

Жыл бұрын

The video was detailing for team -> company. I haven’t used classic vs nextgen in a really long time. I would say that the instructions work for nextgen -> classic.

What about if any of your tasks or epics are linked to a confluence page? I noticed those did not migrate. Thanks in advance!