Assign epics to existing stories next gen

[Jenya Farris]

Can I add the new epics to existing stories, or add my existing stories as children to the new epics?

[Jack Brickey · Accepted solution]

Yes you can do this. Are you having an issue w/ making this happen? You just need to update the Epic Link for the stories to point to the new epic.

[Jenya Farris]

Yes, on the next gen board, I don't have an epic link field on my story tickets. Thoughts? @Jack Brickey

[Jenya Farris]

I actually don't see the epic when looking at it's child story in the detailed view (although I see it on the backlog list), and Epic is not a field which is available to add in my project's issue (when following these instructions: https://confluence.atlassian.com/jirasoftwarecloud/customizing-an-issue-s-fields-in-next-gen-projects-951392551 . html

[Jack Brickey]

can you add a screenshot of your issue view. similar to below. if you have the Admin button then see if you can add Epic Link if it does not show.

[Jenya Farris]

[Jenya Farris]

@Jack Brickey your screenshot looks more like the classic projects, and I have a next gen project on JIRA cloud, if that helps. Seems like epics were just released in this version (https://confluence.atlassian.com/jirasoftwarecloud/roadmap-957979308 . html) 

this screenshot by the way is of a story ticket I created under a new epic, and as you see even on the issue detail view it doesn't show that it is under my epic. But I can see it in my backlog list

[Jack Brickey]

i was reading up on the link you sent. I suspect that you need to follow this article to add the Epic Link given it is next-gen - https://confluence.atlassian.com/jirasoftwarecloud/configuring-the-issue-detail-view-764478043.html

basically you need to go into project > project settings, expand the relevant screen scheme and add Epic Link to the edit and create screens.

[Jack Brickey]

p.s. your links are malformed w/ spaces at the end.

[Jenya Farris]

I know, for me the comment field is not letting me include the link properly, it is giving a malformed html error. Looks like you are not getting the same error?

[Jenya Farris]

I did follow the instructions in that post, but there is no Epic link field in the options.

[Jack Brickey]

links work for me using the link button. and pasting in a copied link.

LMK if you are able to edit the screen. note that you need to be admin for this.

[Jack Brickey]

and you are sure the epic issuetype exists in the project? i haven't played w/ this project type. 

[Jenya Farris]

Unfortunately no, the Epic field is not on the list of possible fields to add to the page (my screenshot above is all I've got, and the points field is a custom one I created because thats not available yet either).

I am the admin, I created our jira instance, but maybe this is just something they haven't built yet even though they released the epic function. I would think it shouldn't be hard to enable the field for us if the function exists. I see they added new start date and due date fields. Any idea how I can request the Epic Link field from someone on their product team?

Thanks for the tip about the link. I was just pasting it into the text box without clicking link first.

Thanks so much for all your help. 

[Jenya Farris]

And yes, they just released the epic type and a roadmap function that I'm super excited to use, but just annoyed that my existing backlog can't be merged in

[Jack Brickey]

ok. so to be clear when you added the project was it "Agility" type? I will take some time today and see if I can play with it. There is so much changing in cloud at the moment and different instances have different features. It is quite frustrating TBH.

[Jack Brickey]

@Jenya Farris, so here is what I have found and bare with me as I don't use Agility as yet so still learning.

1. I added the Epic issuetype to my Agility test project
2. I created an epic (screenshot 1)
3. I added children (screenshot 1). note this is different than classic as you know. Apparently the 'epic link' function is different and hidden in Agility.
4. I found I could move a story to the epic via the backlog (screenshot 2)

[Jenya Farris]

@Jack Brickey You are the BEST! How did you find it (screenshot 2)? Mine says "Change Epic" instead of "Add to Epic" even on stories with no Epic yet, but I am so happy this is there. Now I can go and merrily start organizing my backlog into Epics. 

Thank you again!!

[Jack Brickey]

you are most welcome. I just borrowed from past experience where I could drag issues into epics in the backlog and hope that maybe they carried that forward in some way. I'm actually encouraged by the new Agility and am confident it is going to become part of my daily projects but there is so much changing there I have held off.  Historically there has been too much missing for my tastes but it is clearly getting there.

[Jenya Farris]

I have stayed with it despite the limitations hoping for cool new features. Mostly, i still don't like its usability as much as classic, it feels buggy. However, I am very excited about a truly integrated roadmap without the need for additional software, so I am happy to be on next gen right now :-D

[Erika Sa]

Hey @Jenya Farris @Jack Brickey,

I'm a bit late on this thread but I'm glad you guys figured it out! Next-gen is the new name for agility project. If you want to find out more about epics and roadmap feature in this project, you might find this post helpful. 

If you and your team is using epics and roadmap extensively, we'd also love to hear your thoughts. If interested, please book some time here. We'll send you amazon giftcard as a thank you for your time. 

Cheers,

Erika Sa

Atlassian Product Manager

[Jack Brickey]

@Erika Sa, question for you on agility. Do the standard JQL epic functions work as before? I’m involved in this thread and wondering if it may be Agility related. Feel free to chime in there if you like. I plan to test it out tomorrow.

[Katie G]

@Erika Sa - Per this thread... why can't you add the Epic field to at Story like you can in Classic? So odd.