How do I structure my issues/epics/subtasks for migration project?

[David Frenzel]

Hi, 

I'm currently setting up a migration project in Jira. We are migrating several projects to a new development environment and I'm not quite sure how to set this up and using Jiras features correctly: 

I imagine having one task that has the name of the application that is migrated and which holds information we receive from all the projects. We then have the same sub-tasks (kick-off meeting, technical onboarding, etc.) for every project. On the Kanban board I would like to see the parent task on the card itself so we don't have to add the project name to the title of the sub-task. We want the sub-tasks so that we can better track the status of the individual steps. 

Does it even make sense to use tasks/sub-tasks or are Epics better? 
If further information is required, just let me know. Thanks!

Regards, 
David

[P_D_ Foerster]

Hi Daniel,

I had some migration projects for Jira and Confluence and used my Atlassian Admin Kanban board to track the tasks.
For every migration I created an Epic and configured my board to use swimlanes based on Epics. With this all Stories, Tasks, and so on should group under the epic they belong to.

If you have a sub-task on your board then on the top of your sub-task card there is a line displaying a reference to the parent task.

Regards,
Patrice