As the automation for sub-task is triggered when a Task is created, it considers the Task as the issue. Hence, when we say, { {issue.parent.epic.summary}}, the automation is unable to understand as the Task has Epic as the parent. Update the automation with ' { {issue.epic.summary}} : { {issue.summary}} : Task-1'. It is working as expected for me.
The important points are the epic needs to be in the csv before the stories to be linked to it. Then you can use the Epic Name in a column for the stories which is then mapped to the Epic Link field. Hope this helps you import. Another option if you always have the same set of stories every time you create an epic it may be worth investing some
FPKqO. h60mxlg7vl.pages.dev/470h60mxlg7vl.pages.dev/36h60mxlg7vl.pages.dev/288h60mxlg7vl.pages.dev/325h60mxlg7vl.pages.dev/377h60mxlg7vl.pages.dev/342h60mxlg7vl.pages.dev/94h60mxlg7vl.pages.dev/316
jira convert task to epic
