Link an epic while creating a story in Next Gen project

[Jacob Rasmussen]

When we are creating a new story in our Next Gen project we would like to include the option to link to an epic. I am unable to add this option, and we have to create the story, then click on the link to navigate to the story, and then we can link to an epic. 

[Ash Pitt · Accepted solution]

Hey @Jacob Rasmussen 

If you want to add issues directly to epics there's 2 methods you could look at here in a next-gen project.

Option 1

On the sprint board, select the epic and click "create issue" that will automatically add it to the epic.

Option 2

Add child issues via the Roadmap function (if you have that enabled for your project)

Option 3

If you have enabled the backlog view, and choose to display the epics panel. When you select an epic, it will automatically add any issues you create underneath that epic.

Cheers

Ash

[Jacob Rasmussen]

Thanks for sharing that @Ash Pitt but it actually takes me longer to navigate from my sprint board to either the roadmap or backlog, search for the epic, and then create the issue in the epic. It is actually faster to just create the issue without an epic, click on the issue link, and then link to the epic. 

I'm kind of baffled that there is no option to link to the epic while I'm creating the issue from my sprint board. Do you know the best way to submit this as a feature request to Atlassian?

[Ash Pitt]

Hey @Jacob Rasmussen I updated my original comment to include the ability to do it from the sprint board (it's now option 1). So hopefully that sorts you out :)

As far as raising feature requests, check this out for more info https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html

[Jacob Rasmussen]

I might just be super blind, but I don't see the option to create a new issue on the sprint board. Is that something else that I need to configure/turn on?

I appreciate all of your help @Ash Pitt 

[Ash Pitt]

Ahhh yes - I know why :)

I was showing you the kanban view, how it behaves in the sprint is (I believe) by design and here's my reasoning.

The whole idea of a sprint is to plan the work first. Yes you will find that you will be adding/removing tasks as you go but really when it comes to sprints, if you're adding a new task, it technically should be in the backlog first so you can get the story ready, size it up and prioritise.

Just adding a task to an active sprint is not best practice, and will mess with your burndown chart.

If you're adding tasks to an active board, perhaps kanban is the right approach?

Note: For next-gen there's also an option on the bottom right of the screen to give feedback as well!

[Jacob Rasmussen]

That makes sense 😊 

Thanks for all the help!

[Ash Pitt]

Not a problem at all, happy to help out!

If you're happy with the answer it would be awesome if you could mark the answer as accepted :)

Cheers

Ash