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).
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.
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!
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.
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.
