Next Gen Agile - Epic Children and Annoying Features

[FuzzySmurf]

One of my favorite things about AGILE Classic is that I can make a project plan in confluence, hit 'create multiple user stories' and it creates them all as children for my project. it saves time and makes it easy.
I tried to do this same thing w/ Next-Gen AGILE, and it doesn't make them children! I can however link them 'after' the fact. I tried to find a way to add them after the fact (like in classic) however, it does not  exist. WHY!?

It lets me link, but I dont want to link them, I want children epics. 

Epics however do let me create children, but I then have to manually add them to my confluence project page. This defeats the original purpose of multiple user story creation in confluence!

Also, most of the friendly tools I used in classic are gone.

I am unable to revert from Next-Gen to classic. 

Why! This is extremely annoying as it is!

- A really annoyed, and pissed off project admin

[Angélica Luz]

Hi Alexander,

Just for us to better understand and help you with this issue, can you please give us more details about what "children epics" mean?
Currently, it's not possible to have epic within an epic, only epic with task, subtask, story, for example.

Also, next-gen projects were created to be more simple, to help teams that don't need all the features that classic project has, that's why it doesn't have many features.

Please, let us know more details about this issue that you are facing.

Regards,
Angélica

[FuzzySmurf]

Yes, I'm aware, I switched it back to classic. next-gen isn't ready yet for me.

but to give insight on the issue I was having:
in confluence you can make a project plan (using the default template) and highlight a field. Confluence then gives you the option to make the grid into items. When you make them into items, it defaults to the Epic linked in page properties. this doesn't work.

after making all of the user stories, and it missed the epic link, i tried to re-assign the stories to have the epic I made. it wouldn't let me do that either. 
let me know if i should explain any further.

[Angélica Luz]

Hi Alexander,

Thank you for the details.
I believe that the issue that you are facing is related to the ability to use JQL for Epic link on next-gen project, which also affects Confluence because it uses the same JQL as Jira.
- https://jira.atlassian.com/browse/JSWCLOUD-17239
Can you please check and let us know if this is the issue that you are facing on next-gen projects?

Regards,
Angélica