Need to search for issues by epic and epic by issues.

There is something not entirely clear on the Story Detail view. Upper left needs the Epic Icon. so xyx-3 /  xyz-42

Or perhaps it's overkill but Having the Epic Listed in the Area under the Description same as where the Stories are listed on the Epic detail card. I think it would help and provide continuity to the information being viewed.

Hi indrek5 and dan291554704,

Let update my original comment to say "For the initial subtask release which gives the JQL ability to use "parent =", Parent won't be a field on the issue".

You are correct that we need to solve the problem of:

1. Finding issues for an Epic in Basic search
2. Seeing which Epic is the parent of a given set of issues for the list view and exported data.

We are working on it and I will keep you updated as we progress and have more info.

Regards,
Nathan

Stop the presses, I think if you create a new bug it'll get marked as a duplicate3 of this one ; **https://jira.atlassian.com/browse/JSWCLOUD-17758
Perhaps best to vote that one up instead....

NP! Welcome to JIRA!!!! You might not think it reading all these issues and stuff but it really is a great tool!
You are correct though, it should be a subtask under https://jira.atlassian.com/browse/JSWCLOUD-17392 , just like this issue is a subtask under the same issue.

I think (my memories shocking at the best of times) you'll need to create it as a bug though, and when Atlassian traige it they'll assign it as a sub-task for next gen projects...

Hahaha. Thanks, it's my first day using Jira

(I tried creating a subtask, lol)

Hey Eric,

Just so your not waiting for Nathan, if you look at the top of the screen (this screen) there should be a blue "Create" button

Can you please provide a link to where you would like the ticket entered? @nsturgess

Thanks

Hi Nathan,

Trying to teach non technical AM's JQL would be a struggle, their eye's glaze over as soon as you say any common techie buzzwords or acronyms like "SQL", "Query", "MVC", "CMS", "Inheritance", etc. It is a shame its not exposed as a field value as @Indrek Petti refers to, As a workaround I guess I'll have to set up some saved filters and work out a way to roll that filter with each new project without having to manually configure.

I realize of course you're focused on the JQL aspect, and not so much the GUI of the Issues and Filters screen, so does my comment re the "Parent"/"Epic Link" simple control belong on a new issue? I don't think you should lose sight of that, as I'd bet most users will try the basic Epic Link field first time when trying to filter by Epic in a Next Gen! Happy to raise a ticket and/or vote up an existing one...

@Eric Wyman, this is a really important feature/bug as well. I completely forgot about import! While I do suppose you can at least Bulk Assign issues to an Epic so the manual workaround is not so bad, this is a really important part of the Import and Epic set up. Please do post back if you make a link to the issue you create (if you do) as I'm sure a number of the followers on this thread will vote that up as well.

Hi Nathan.

Can you be more specific what is exactly implemented right now and how it is going to work/what is not working in the same way compared to classic epic link?

You said "Parent won't be a field on the issue" - does it mean that we can't show it as a field in reports?

Hi dan291554704,

Sorry to say that the parent = solution won't help you with basic search. I just want to be upfront about that as to set expectations correctly. Parent won't be a field on the issue (like Epic link is in Classic), so it would not give a dropdown with values like you are requesting.

So we would need to address that problem separately. I know that is not what you want to hear at this stage, so appologies. Can they be given a basic tutorial in JQL as a workaround, so that they can be unblocked?

Regards,
Nathan

Hi eric_wyman can you open a ticket for that please as this ticket requests:

JQL to return issues that are associated to an epic as we can do for classic projects.

That way we can make sure it is tracked.

Regards,
Nathan

Adding back in the perspective that this feature also impacts the import of issues via csv

There is no way to tie stories to the epic link and would assume that when next gen issues contain values under Epic Link importing should be usable as well. 

Our team moved away from Jira NextGen and restored classic Jira projects. Nothing to blame to the Jira developers, but I think this was not a mature product to release.

Hey Nathan,

So happy to see this being worked on. Quick question regarding the above, If asy one of our Account Managers not using JQL (because they don't know how) and are using the "Epic Link" dropdown in basic mode via the Issues and Filters screens, will the above still work (i.e. show a list of parents if its a Next Gen, or Epic Links if its classic)?

Just to clarify what is being worked on here, as I want to clearly set expectations.

When we release subtasks there will be a way in Next-gen to get all the children of a parent issue by including the new JQL query of

parent= 

This will enable users to query with an OR statement to get the issues that relate to Epics from both Classic and Next-gen, e.g.

Epic Link = <some Classic epic> OR parent = <some Next-gen epic>

Glad to see that this has been picked up for development.  Any chance that we might have an idea of when it will be live?  We're going to revert back to classic if this is not available rather soon.  Thanks!

Looking forward to the delivery of this most needed functionality !!! It is a requirement for my work as PM

When I discovered next gen after being away from Jira for about 1,5 year I got super happy and everything seemed great, at first.

I've spent the whole day discovering missing features, bugs, bad UX and LOTS of other problems.

Sure, moving stuff back to classic is an option, but based on how long it's taken to fix this basic functionality makes me want to leave Jira for good. 

I'm very disappointed that Atlassian hasn't been able to fix this in over six months.

"Next gen" doesn't even feel like an alpha version, more like a basic POC made by some students studying beginner level programming.

@jason Creak - There are enough other failings of NextGen that we pulled all projects from it and reverted them to Azure DevOps or Classic Jira.  NextGen is a confusing step backward for the professional management of projects and not recommended.  Good luck!!

Thanks Jason, on review and further reading (on Premium) you're right, it's a little ambiguous if you read that page on its own but the big old "Premium" in the title is a good indicator! Guess I was stuck in the context of this ticket so my bad.

Thank you for the clarification and reassurance Ben! Hopefully the fact it has eyes on right now means we should see an incremental update on cloud soon <fingers crossed>

Hi Ben, Nathan,

Thank you for taking the time to keep us informed. I guess end-of-month reporting has us all eager and vocal. Looking forward to the implementation!

Thanks Ben - that clarified a lot - but yes a real approx ETA would help us decide whether to drop NextGen for now or not.

Ben - Thanks for the update .

We are eagerly waiting for the ability to use JQL for filtering child issues for an Epic. 

Could you please update the status of this item to In Progress or Under Development? That will give the wider community an assurance that it is being worked upon.

Hi everyone (I'm a PM on Jira Premium), I can confirm: 

1/ the Epic Issue type and below (including JQL) are standard features for both next-gen and traditional projects.

2/ I can't give you an exact eta on the JQL fix but can confirm it is being worked on right now and not in some queue for later on

Just to clarify the 'Premium Features' we are working on, these are related to Advanced Roadmapping: Visualising more hierarchy, dependencies and forecasting (Plus more to come). Standard roadmaps can still access all the story level tasks by clicking the epic on the roadmap as we currently do.  
https://confluence.atlassian.com/jirasoftwarecloud/premium-roadmap-features-968680505.html

Hope that clarifies things.

HI Nathan and Dan.   

With respect I think its hard to misread https://www.atlassian.com/software/jira/premium and https://confluence.atlassian.com/jirasoftwarecloud/premium-roadmap-features-968680505.html - they imply that "Roadmaps with hierarchy" will become a paid Premium feature (for NextGen projects) once "early access" is over.

To clarify things, @Nathan - can you confirm:

1.    Epic and issues below Epic (surfaced in JQL) will be a Standard feature for both NextGen and traditional projects.

2.    What the ETA for release for this issue for NextGen projects? - ie whats predicted by the Roadmap feature today 

I Think Jason and yourself Scott have misread the article Jason links too.

The ability to try this feature now, as a BETA is what is only available to Premium users. The feature itself is core, and once past testing and ratification will be pushed into the core product.

At least that's how I read it, I'm just a user, not Atlassian affiliated!

Wow. Thank you Jason for pointing that out. I did not realize there were going to be "premium features". 

I'm totally fine with paying more for better products, but they have to actually work. 

Question for @Nathan Sturgess then... why does it say premium feature there but you're saying otherwise? Hmmm?

Thank you for the feedback Nathan.

What does we are on the case and working on it mean, the status says awaiting development which would indicate that it is sitting in the queue waiting for a resource to work on the issue, Given development has not started and take into consideration testing, and product release that we at least a month away, most likely more before this feature is delivered. 

what is the priority of this issue?

Is there a process for escalating issues or requesting to move this issue up on the priority list?

Looking forward to your response.

Thank you Nathan, I think sometimes a bit more visibility may be useful.

I know that you do not want to put a lead time on the feature but is there any indication of a time frame?

Hi jason.creak and michael.trice, sorry that you don't have this JQL functionality, we are on the case and working on it. So please hang in there, we know you need it.

"View Child Issues of an Epic" is now becoming PREMIUM (!!!) functionality

Epic and issues below Epic are a standard feature and will remain so. So don't worry.

Regards,
Nathan

If this is true, then we may have to move away from Jira sooner rather than later.

We have only been using Jira for a few weeks and had expected this feature as standard.

I really cant believe this.    It renders any custom management reporting virtually impossible.

Curiously "View Child Issues of an Epic" is now becoming PREMIUM (!!!) functionality (https://confluence.atlassian.com/jirasoftwarecloud/premium-roadmap-features-968680505.html ) which could explain why this function isnt available (nor apparently through API from comments above).

This is starting to feel like "product differentiation gone wrong" or worse.

We recently switched to JIRA. I was expecting this functionality to be implemented swiftly as I do not understand how you can to basic reporting without it. I would have to move to another solution very soon if I can not even have an idea of when this should become available.

This is has been outstanding since October 2018 and from the long list of comments, has an impact on a large number of users, is there an ETA on when this will be resolved?

With the growing number of Epics and of course child issues, it's very important for our reporting requirements to export the list of open / closed issues under an Epic. In my previous organisation JQL was the solution for many of the reports and was the strong point of using JIRA. Please enable JQL with Epic links for next-gen projects.

Sorry to shatter your hopes but it seems that there is again noone from Jira development side dealing with our problems right now...

I have resorted to writing a selenium screen scraper + API extracts to get data in an tabular format that has issue + epic for each row in the table.

Hi Nathan, 

I can just echo all the various use cases others have mentioned. Ours is around teaching old dogs new tricks. 

We just had a shake up of project managers on a project. We got in someone brand new who was thrown in the deep end. He was trying to use spreadsheets to manage but it got WAYYYY out of hand, so we wanted to suggest he move to Jira (where the rest of our projects are as well), but he doesn't have time to learn it. We picked nextgen because it's simple. One REQUIREMENT he has was the ability to export the various issues in a spreadsheet to share with the customer but without ability to group by epic in the export it's all manual.

Also, we are deploying confluence and plan to have pages for specific epics with the various tasks. There's not currently a way to show just the appropriate tasks/stories by epic. So really, we just need JQL support for epics. 

Hi Nathan,

I would like to be able to use the rest API with JQL to get all issues that belong to an Epic.

parentEpic() doesn't work either.

 This is an extremely useful feature. I would love to see this implemented. Countless uses to search by Epic.

@Dan Walker Thanks for the tip! We are a small team using Next Gen but in a much larger organization that is mostly on Classic so I want to watch our spending with the Add-ons that don't have wider-spread application.

@Emily Spitzer, We went with the Swanly Release Plugin until Releases and Versions make their official return (It's on the roadmap apparently}. It is paid for but if you're on a small team like us it delivers versions and releases quite nicely.

Hi Nathan,

Having this would be an excellent way for me to create a work-around for not having "release versions" in next Gen. I plan to label use "epics" as a way to track version releases, and if I have this functionality I could show what fixes/new features were released together more easily, using a confluence report I have already created.

Hi Nathan,

To me, explaining why do we want to be able to search by epic in a project management tool sounds weird. Let's say, it is needed for almost everything: reporting, progress tracking, project clean up, etc. Thanks.

We are in the process of rewriting our web app while keeping our legacy version stable. We moved to next-gen boards mostly because of the roadmap feature and how nicely epics are laced into the process. We have separated our epics out by 1. Legacy/New app and 2. Work type (authentication, security, features, etc.). Our board of directors is watching our development productivity and monitoring how much work we do in each area of the product. We expected to be able to export all of our issues (filtered or raw) and have the epic included, so that we can easily show our board how much work is done in each area without having to get them into Jira. 

Is this the very definition of an "Epic Fail" ?

We provide an integration of Jira into our product. There is a functionality to connect a project in our product to an epic in Jira.

In another view the user is able to view all issues linked to the epic and see if those can be completed inside the given time frame. This works great with classic project, but due to this issue not with next gen projects. Therefore we had to disable the feature entirely for next gen projects. 

For me, as above really. My primary use is within JQL via Issues and Filters screens, or via custom issue views/lists (such as JQL within a Confluence Jira Macro. My Managers and Directors would want to use it for reporting and calculating velocity, as the roadmap follows the Epic pattern progress reports broken down by Epic are useful, or Stories/Sprints broken down by Epic as above have mentioned also.

I should note that in addition to Epic Link patching within JQL, the Basic search Epic Dropdown does not correctly pick up (or thus filter) the Epics on the Next Gen project either. Not all our managers are technical so trying to explain JQL and Advanced search to them is a pain (We can't even create a pre-defined filter based on epics for them ATM).

Also, again as above (though I assume fixing Epic Link will fix this also) sorting by Epic within Issues, Filters and Confluence Jira Macros.

Another situation of note, specifically relating to migrating classic projects to Next Gen and/or linking to a previous project that is Classic from a Next Gen, it appears the epic-name attribute does not exist in Next Gen Epics, so you can't assign a classic issue to a next gen epic, as describd here : https://community.atlassian.com/t5/Next-gen-questions/Can-t-Link-other-project-issues-to-next-gen-epic/qaq-p/937372

It would also be good to sort out the ranking/order of issues within Epics, Sprints and Boards, as well as sorting Epics within Stories, Sprints and Boards, but this is a different issue so please all vote for this issue too if epic / epic issue ordering is interesting to you : https://jira.atlassian.com/browse/JSWCLOUD-17284 & https://jira.atlassian.com/browse/JSWCLOUD-17590

Hi Nathan

Our process is to manage multiple products and projects using a single board on a classic project with a shared filter containing all teams, products, projects in our company in a shared sprint.  We manage this board with filters when planning and prioritise the backlogs, plan epics, plan sprints and do resource allocation using this one board to get an overview and reporting at a company, product and project level which then filters down to each product team. 

Currently without the epic link only classic project epics show on the board epic side panel, all Next Gen epics just display as unlabelled-epic and none of the tickets associated with that epic lists or adds to the issue count of the epic.

We use the epic and version sidepanel extensively when planning and not having any visibility on the epics from next gen projects means we need to start planning on project or product level and then try and work our planning back up to company level.  This isnt ideal and since next Gen currently has no editable board queries there is no good workaround for resolve this.  

Adding to other users above we also use the JQL queries for reporting as well as displaying on confluence and without the epic back to the individual tickets Next Gen epics isnt of much use other than on the Roadmap for Next Gen Projects

Hi Nathan,

We manage different aspects of our projects using Epics.

Our reports to project stakeholders include a summary of the key Epics in focus for a given sprint. We want to show status of the issues associated with each Epic as part of our reports. We currently have to maintain a manual mapping of Epic -> Issue in order to generate our reports. We would like to be able to use JQL to query the issues associated with a particular Epic.

Hi Nathan,

• We manage our projects by Epics and then use stories and tasks to segment the work.
• We use Jira and Confluence as reporting tools we share via screen sharing with clients.
• We rely on JQL queries and Epic Links as a way to easily list all stories and tasks within an Epic (in out case project) which we can export as a PDF etc. for reporting to clients.

We have banned Next-Gen projects until there is a solution.

Hope this helps.

We use JQL in our Plugin EpicSumUp to search for the linked issues via REST.  We had to disable our Plugin functionality for next gen epics, as we are not able to collect the needed information.

As soon as we have a way to find the linked issues in any way via REST, we should be able to enable most of our features for next gen projects

As a user I'd like to be able to use issue search to view all the issues in my project including the epic they are linked to, in order to extract the data from Jira to complete monthly reporting where I can group issues by associated epic

I am considering migrating to a classic project to avoid the overhead of labelling every story with an epic label, which seems to be the only workaround

In Confluence, I use(d) a Jira Macro to show all tickets for a specific Epic, to have an overview of all related tickets.

For the information how we are currently “solved” it is before me move stories to done we add manually a label what contains the epic issuekey value

Hi Nathan!
Issue what I’m trying to solve is
1) we can visually drill down from epic to stories but if I open story first (from jql query result what happens when I want to see storied completed long time ago) then there is no indication on the story screen that it is related to any epic at all.
2) if I want to do Automation for Jira data manipulation scripts than there is no epic-story link what I can use
3) I need monthly completed stories report what is grouped by epics (Epic should be a visible column for each story in jql query results).
4) Epic report (like in classic scrum boards) would be nice

Hi Nathan,

We have to prepare a monthly report of time and points spent per Epic duriing those calendar days. Each Epic is tagged for being Capitalised costs or not and if it can be claimed for R&D rebates.

My Current JQL looks like this

project in ("Product and Technology") AND Type = Story AND (status = Resolved OR status = Done) AND resolution = Done AND resolutiondate >= "2019/03/01" AND resolutiondate <= "2019/03/31" ORDER BY cf[10300] ASC, cf[10004] DESC, cf[11802] DESC

I can then sort this by column name Epic link then review and sum up the points and hours for tickets in the epic.

Hey Nathan. We use epics to track marketing campaigns, linking issues (pieces of content) to a specific epic. We would like to use JQL to pull issues from a given Epic (Campaign) into a Confluence document.

Right now, we can use the "View in search" feature (available for child issues of a next-gen Epic) to create a filter that includes these, but if we add new issues to that Epic they aren't included in the search. It would be great to use JQL to say "Pull every issue linked to this Epic" and add them into a Confluence page easily.

To answer Nathan: I like to retrieve stories from multiple epics in the issue search screen (using JQL) so that I can select multiple stories to bulk edit (and not necessarily all the stories for an epic either, if might be stories from Epics X and Y and are assigned to person Z or have status Z, etc.). 

Hi guys,

I know you guys really want this functionality, I am sorry that it is hindering your use of Next-gens. Can you please reply here and tell me the problem that you are solving by using Epic link? As I am looking at JQL in Next-gens.

An example of an informative response being: "We use epic link to search for all the stories in an epic, so that we can export the logged time to an excel document, so we can bill clients".

Regards,
Nathan

Hey! Thanks Atlassian for hearing this issue and assigning it for development!

Obviously this issue has gained traction with the uptake of Next Gen so I think I speak for all above in expressing our thanks for looking into it!

@Dave Mahoney, there is a roadmap here : https://www.atlassian.com/roadmap/jira-software?_ga=2.225715794.978772590.1554802788-950940185.1542796952 but it doesn't really address the issues on the service desk for next gen projects : https://jira.atlassian.com/browse/JSWCLOUD-17392

Piling on here, it is really amazing that I can't view/manage my epics WITH their child issues in next-gen projects. I also advocated for the switch on my team to 'simplify' our process and ended up regretting it. I feel the Jira team should have better communicated the limitations of Next Gen as part of promoting it so folks can choose to make the leap or not with eyes wide open.

At a minimum there should be Next Gen roadmap so we can decide to stick with it or not.

Seeing as this ticket was last updated on Jan'19 and that Jira is not interested in doing anything about this anytime soon, I'm just going to stop watching this ticket. Hope they come up with a solution eventually. I'm not counting on them and so shouldn't you.

Bye

Too bad that the [user story maps app|https://marketplace.atlassian.com/apps/1212078/easy-agile-user-story-maps-for-jira?hosting=cloud&tab=overview] cannot be used with next-gen projects.

Courtney,

Great article about SLC! Thanks for sharing.

Also, the fact that this ticket was made in OCTOBER of last year and it still has not been addressed with almost 50+ comments and 250+ upvotes from your USERS is interesting. What happened to user first development? Read this: https://www.pactsafe.com/blog/why-pactsafe-uses-slc-not-mvp-for-product-launches

This seems like a basic function that your users would need to have. I have been working to get my dev team over to the next-gen boards for 4 months (which was a pain in itself for a lack of a migration process). And now the only way to have this basic function is to SWITCH BACK? What an experience...

Not being able to filter by epics is a crucial component of monitoring for our team. Our CTO personally had to take a week of his time to re-label everything in our system, finished and still in the backlog, that we have retrospectively organized and placed in epics so that we could provide crucial reporting to our board of directors on our progress and productivity. This messed up all of my slated work and I missed several deadlines from this, so not only is it affecting our business, but my supervisors are less than happy with my work as of lately for an issue that lies with Jira, not my performance. 

Please provide this basic function that otherwise should have been included in the MVP product of next-gen boards, and especially this late into the product's life. It is embarrassing that a software like Jira could oversee such a critical usage. We will begin looking for alternative products for our scrum process if this cannot be resolved quickly. 

Previous projects here used VSTS (Azure DevOps) which has a lousy wiki and OK Agile functions.  Got them to use Confluence as wiki even though it doesn't play well with DevOps.  Project finished and the project team was convinced to switch to Jira to gain functionality and integration with Confluence.  

The total inability to search, filter, or display Epic information related to stories makes this product close to useless.  What happened???

We will finish this project in Jira because we are too far invested in it, but there will be no more Jira projects unless this is fixed.  Our licenses will expire with this project and that will be that.  I will not be able to (nor will I try) to get people to use Jira in the future.  Sad.  It was a better product.  Now it is not.  Please fix ASAP.

This is also an issue for rendering timesheet reports. Epic Link column is totally blank and we are unable to effectively report on what we're working on.

Extremely important issue

Agree with others, please implement this feature.

This issue is super important – it makes any of the Confluence integration stuff like Project Plans completely useless, because I can't use a JQL to show issues that belong to a specific epic.

More importantly, there are sections of the UI that are misleading or just don't work due to the fact that this isn't implemented yet.  For example, clicking on the search ICON from within a project, I get an app notification that Epic Color, for example, is not applicable to my selected issue type (in this case, parent is epic), but using any of the epic filters simply don't work, even the ones I can select.  That's a terrible UX, I had to come and search for why this wasn't working, and to find that it's just simply a lack of a feature is super disappointing.

A lot more traction for this lately, the more I try to deal with it from a guerilla style just get the project going stand point the more i think this is genuinely not a feature request but a bone-fide bug. when you view the issues from the "classic" Issues and Filters screens it lists them as epics however if you edit one the type selector at the top reports field misconfiguration for the type, you can neither save the epic as an epic or change an issue into an epic.

Just trying to set up a a heuristic "all my issues" filter is of questionable worth if you can't actually sort or filter on the Epic link, not to mention the frankly "somethings missing" look and feel of the list view without an epic column.

Fingers crossed it can be hot fixed quite easily and the increased traction promotes this patch soon.

Please add this feature to allow for comprehensive reporting while using the Next-Gen model. Thanks.

Please build this feature. 

This is a really important feature, without it NextGen projects really lack basic functionality. I do not want to go back to OldGen, so please build this.

I have reverted my projects back to the old Jira (which was a complete pain to do). NEXT GEN Jira is not usable without this fix. 

Well, I've been working all day on a new Jira project for a client, using their Jira integration which only allows for Next Gen projects. This is the 5th issue that I've found "No longer works in Next Gen" or "Not available in Next Gen" (Releases, Versions, Controlled Workflow Transitions, Time Estimation & JQL Epic filtering). We are now waiting for the Admin to enable Classic projects and rebuild the entire thing. +1 for this from me...

PLEASE BUILD THIS

Any updates on this? I am in the same boat as many others here, and considering going backward to the classic project.

This is a deal breaker for us as well. We have some tools using jql to generate statistics and so forth, and we need to be able to query the epic that that a story is part of. 

Same here, this is a must and will be a deal breaker. Any timeline on this becoming an addition would be appreciated.

It's been 5 months since this was raised and my project stakeholders are understandable getting frustrated at the lack of progress and information from Atlassian on this subject. Can you provide a clear indication of when you intend to address this issue?

We need to make a decision on whether to revert to the previous generation of projects or whether to hold on for a fix for this.

Pretty sure this is costing you sales, as several of our customers where planning to migrate to Atlassian tools, until they became aware of this fundamental limitation with next-gen projects!

Same problem here too - standard project status dashboards no longer work for next gen projects. I was loving it up to this point, but need to consider rolling back now. 

In our company we decided to rollback to the Jira classic projects. It will be painful, probably we are going to lose some data, like custom fields and linked issues.  After all, the next-gen project is undeveloped and we can't see hope. Almost six months to introduce a simple epic filter, it is too much for us.

Just ran into this problem today. Having to tell people that I can't pull reports out of Jira based on epics was embarrassing. Not something you really expect to test before moving to a next gen project. I mean you have epics, you have stories assigned to epics, the logical conclusion would be the ability to report on that link.

Surely this is MVS? Not having this makes Next gen projects virtually useless. the fact that this is not even included in the REST results means you can't even follow that route. What were you thinking?

This feature is also crucially important in my team. We need to provide reports and feedback on specific epics and we are unable to do that without epic link filtering. We are thinking about going back to separate non NextGen projects to handle this request!

This is extremely frustrating. My CIO wants weekly reports on what my team is doing each weekly sprint, and there is no way to export the list of issues associated with a sprint and include the epic information? When is this going to be completed? I took it for granted that such a basic reporting feature would be available as part of the MVP.

Sad faces all round this week in our office. No option to report on Epics Link in the Next-Gen experience. Our mature reporting tool served up doughnuts after trying to migrate to the Next-Gen project.

Back to Scrum Board we go.

I can give business cases what totally breaks this new epic concept. 

Lets say we need to know 2 things:

1) How many stories per epic were completed during month/week period time. Any reporting is available only when we use sprints and even then there is no epic report but just overall total. We can't use any other way as link to those new epics is only visible inside built in next-gen graphic interface (see my next case when even this gets broken). 

2) Not possible to see later the epic to where this completed story did belong to. If the story is marked as done and the sprint is closed or if the time it stays on done column is passed, it can be found only through "done issues filter" (as it disappears from the backlog and from the board what seems to have the only places what know how to show the link to this next-gen epic) . But this "done issues filter" shows only the story card what doesn't not contain any reference to next-gen epic. Like it was never related to any epic. 

This stuff is so broken and creates some confusion as users are directed to use next-gen projects and functionality build around epics (roadmap) but after we have used it and then need data - the basic needed functionality is not there rendering our user experience to worthless disappointment. Jira is supposed to be a tool for managing important process related information - it is business critical to get it right, guys  

What should be in place:

1) show related next-gen epic name in story card as well

2) Have a epic related reporting

3) Make Jira filter script language to support this epic link field and also show it on results as a field

Ditto to the above; really need this feature !!!

Without this feature it is impossible to report on next-gen projects properly. Please add this functionality ASAP.

This is a crucial feature! Without it proper reporting is not possible. Please Jira Dev team, move this up the list ASAP 

+1

Not having this feature makes grouping tickets with epics outside the actual next gen project impossible. This is a vital feature that needs to be bumped up in the priority. Please tell your colleagues to vote for this issue. 

This literally renders Next-gen USELESS. Please fix ASAP. 

I for one, would very much like to hear an ETA on when, if at all this will be supported. Without the epic links, reporting on these next-gen projects is impossible.