I'm interested in leveraging the Next Gen functionality, but want to keep the hierarchy of epics and stories (i.e. you can link multiple stories to a given Epic). Does anyone know if this is possible in Next Gen?
You can do this in the next-gen scrum and kanban.
Hope this helps.
(Step 2, you go to the Board to select either one story or more than one by using command or ctrl)
However, please check/watch for updates on this related in-progress issue:
@Jason LaCarrubba we're looking to rebuild the create issue screen for next-gen in the medium term and we originally were planning on bundling the assign to epic change with this work - given we have received some feedback around this, including yours, we'll look at the opportunity cost of investing in extending the existing create issue in the short term. I can update when we have more info. Thanks for your feedback
My guess is that not everyone refers to them as "Epics" and so the "Add to Parent" option is there to support Jira users who have created custom hierarchies. There are examples of custom hierarchies where people use "Episodes" and "Sagas" .
This is just a guess. Maybe there is someone from the Atlassian team who could speak on behalf of the product.
@Laura Bowers and @Christian Zelada It is 'Add to Parent' for a few reasons. As mentioned by @Mike Solomon not everyone calls them Epics (you can rename that level to something relevant to your process).
The second reason is that in the future Next-gen projects will support more levels above epic and so 'Add to Parent' will become a common pattern.
Also supporting @Jason LaCarrubba's point from here. Can't wait to be able to select the parent issue in the creation window!
I would like to suggest also that the parent issue should be more visible in the edition window for an issue, right now it is kind of hidden at the top, it would be very nice to have it like in the classic view, as a tag with the epic name and backgrounded with its color.
I have to say, this is the WORST UX. Using the Jira Mac app, my workflow is:
I don't have words for how irritating this is. Frankly, it is a good example of the type of encumbrance that has long plagued Jira and has damaged its reputation.
Please allow us to link an epic when creating an issue!
I reported this issue - as I want to be able to search Issues by Epic and the JQL search doesn't work. The Atlassian support team agree and a bug has been raised for it
I hope it gets fixed, as this is pretty fundamental to be able to work with Epics in NextGen projects!
I am having the same issue and really agree that if this is not working then how can we use the next-gen projects ???
Answer is we can not...
Ditto. I've just convinced the project team to switch from Azure DevOps (VSTS) to Jira. One of the main reasons was you could not show which Epic a story was tied to in a VSTS query.
How dumb that it can no longer be done in Jira.
Agree that classic Jira was complex, but at least it worked.
With the release of subtasks you will be able to use an OR statement and parent = in Advanced JQL to get the Epics from both Classic and Next-gen.
An example of such a query would be:
"Epic Link" = NPC-6 OR parent = NJDP-5
There is a subsequent body of work that we are just about to start that will give:
That sounds great @Nathan Sturgess . Just to be clear:
As a user, I would like to be able to do this:
- When I create an issue i want to be able to link the issue to a parent (so in the create issue screen)
- When I view an issue i want to be able to see/edit the parent (directly, not via a sub menu in the right top corner)
- When I search for issues i want to be able to see the parent
- The parent link should be clickable on which a screen opens which shows me all issues (childs) of the parent
I hope this is not too much to ask? Is this something we can expect this year? (we might move back to the previous gen project if epics/parent links are kept hidden in next gen projects)
No, not too much at all.
- When I search for issues i want to be able to see the parent
This is next up on my roadmap, we are just finishing some Epic API work and then we will pick up that work.
I will ping internally now to get a response on the other points for you.
Hi @Rogier Simonis | MKB Brandstof - we'll be looking to iterate on the visibility of and interaction with the parent within the issue view very soon. Send me an email to firstname.lastname@example.org if you would be keen on being part of some exploratory testing around this. Thanks
Look under the Roadmaps section. Those are epics you can scale to timelines. Pretty neat.
Although the language and means to do things is frustrating and entices anger. Probably why you couldn't find it.
So epics are called Roadmaps... and Parents. If you want to create an epic you go to Roadmaps. If you want to assign a ticket to an epic you say "change issue parent".
You cant add sub tasks to anything. So instead treat epics as stories and sub tasks as tickets.
I know right... good luck
This and all the dialog we have seen on related threads indicate that Atlasians is got with their paints down, a deer in the headlights, and has no concrete plans to deal with it.
In fairness, a few years ago, I applied for the job of the person who is leading this effort. They failed our community.
I'm looking for alternatives.
Clubhouse has been pretty great, actually. I've been setting all my new client projects in that tool and haven't looked back.
Simple to set up, and best of all, it just WORKS!
No roadmap tool yet, but from the looks of it, Jira doesn't offer a useful roadmap tool either. I supplement TeamGantt for any roadmaps needed - the first project is free.
Unfortunately, some clients are tied to the hip with this software.
LOL.... not do distant future measured in years. I just converted my project to classic. Took about a day and disrupted the reports and links other members had set to the old project.
You're done. Easy peasy. 10 hours + out of your schedule.
haha! Literally how it works. Spending time trying to save time spending.
Thanks for your response but I cant do that. I shouldn't have to do that is my thought. I shouldn't have to accept poor testing in 2019. What happened to Beta testing. What happened to user feedback. What happened to focus groups?
Just disappointing really.
Thanks @Mark . The challenge has not been how to add NextGen stories to an Epic. The challenge has been how to use the Epic/Story link in more advanced features such as JQL queries, reports, exports, view results on a Confluence page...
All our projects have been switched to classic Jira or back to Azure Dev Ops so we are no longer impacted by NextGen.
I will say that it is a different experience than classic projects. There is no Epic panel in the backlog and it seems like JQL to find child issues is not the same.
@Mike Solomon I hear ya!
I asked them what's up with that, here is the answer:
Indeed, with the Next-Gen projects and Epics being launched we can't use the Epic Link field to return issues that are linked to the Next-Gen epic as we can do for the classic projects.
I have it reported to our product team here to give the ability to use the issue navigator to return issues that are linked to a Next-Gen Epic.
Unfortunately, we don't have a different workaround to achieve this as the one that you already mentioned.
Christian, I strongly recommend you to vote in this feature request and drop a comment to let the product management know about your use case. By doing this, it will ensure you're proactively informed of progress and updates going forward.
Hi @Tomas Boman
There is no notion of "Epic Link" or "Epic Name" fields or columns in Next-gen. They actually don't exist at all on the backend. The name that is shown on the board and in search for Next-gen base level issue types comes from the parent Epic's "Issue summary". So "Epic Link" can't be "populated" because it doesn't actually exist in Next-gen. But there is the "parent" as mentioned by you.
What are you looking to do exactly?
Weird that you say"Epic Link" doesn't exist in nextgen project. When I the query filter and choose to show the "Epic Link" column for my nextgen project, some of my tickets do indeed have a populated "Epic Link" value. The parent epics belong to an old-school project, but the stories in the epic belongs to a nextgen project. Perhaps that is a bug that we have been exploiting?
I am using 3rd party apps in Jira Cloud, which can only group on "Epic Link", not on "Parent". By manually adding my nextgen stories to the corresponding classic epics, I can run reports on "Epic Link", but I have to manually add them and make sure they match their parents.
I was hoping there was a bulk edit that could do my manual work for me.
A work around I have had to use instead of going back to the legacy project is to add a label field, each task / story created I can then use the following jql query in confluence to pull back jira's per epic.
project = "project name" AND "workstream label" = "label id"
Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events