Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17392 Team-managed software projects
  3. JSWCLOUD-17239

As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • None
    • None
    • next-gen

      Atlassian Status as of 12 December 2019

      Hi everyone,

      Customers can query on Next-gen epics using the parent =. If you want to combine Epics from both project types, an example of such a query would be:
 "Epic Link" = NPC-6 OR parent = NJDP-5

      The Parent field can now be selected as a column in the Global Issue Navigator and exported from Jira.


      Regards,


      Nathan Sturgess
      nsturgess@atlassian.com

      Product Manager, JIRA Platform

      Original request description

      WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects.

      Steps to reproduce

      1. Create a next-gen project
      2. Create an epic
      3. Associate multiple issues to the epic
      4. Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic
      5. No results are displayed

      Expected results

      Return the list of issues that are linked to the referenced Epic

      Actual results

      Use parent() function to show the child issues of the Epic. Example:

      parent = EPIC-123
      

            [JSWCLOUD-17239] As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics

            Kyle added a comment -

            If this isn't implemented (and hasn't been for a year), why must a non-removable "User Story Map" item appear on my Jira sidebar?

            Kyle added a comment - If this isn't implemented (and hasn't been for a year), why must a non-removable "User Story Map" item appear on my Jira sidebar?

            Has this ticket been picked up yet?

            I don't know how you prioritize work . But, this seem to be basic and highly impacting multiple teams.

            Kakarla Aravind added a comment - Has this ticket been picked up yet? I don't know how you prioritize work . But, this seem to be basic and highly impacting multiple teams.

            Echo-ing those above, this has been the biggest pain-point of Jira for me. I need the following capabilities:

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

            The lack of this basic feature (for over a year) adds hours a month to my workflow.

            I used to defend Jira in conversation when someone would complain about it.

            Now, I am actively and vocally telling people in my circles to avoid Jira becasue of this basic missed requirement.

            Jonathan Kaczynski added a comment - Echo-ing those above, this has been the biggest pain-point of Jira for me. I need the following capabilities: Finding issues for an Epic in Basic search Seeing which Epic is the parent of a given set of issues in the list view and exported data. The lack of this basic feature (for over a year) adds hours a month to my workflow. I used to defend Jira in conversation when someone would complain about it. Now, I am actively and vocally telling people in my circles to avoid Jira becasue of this basic missed requirement.

            I agree with @rma's comment ^. This is exactly what I've been researching and trying to accomplish as our team moves from classic to next-gen. In order to properly report back to business stakeholders, I need to show a table of issues with their associated parent/epic link. Thank you!

            Elizabeth Nixon added a comment - I agree with @rma's comment ^. This is exactly what I've been researching and trying to accomplish as our team moves from classic to next-gen. In order to properly report back to business stakeholders, I need to show a table of issues with their associated parent/epic link. Thank you!

            I'd like to add an acceptance criteria: 

            The epic link and epic name (or parent link and name) should be displayed correctly in the issue navigator. 

            Currently that is not the case. To my knowledge there is currently no way to get a report that displays all issues and their epic. Which is one of the most basic reports I want to present to stakeholders.

            Robert Masur added a comment - I'd like to add an acceptance criteria:  The epic link and epic name (or parent link and name) should be displayed correctly in the issue navigator.  Currently that is not the case. To my knowledge there is currently no way to get a report that displays all issues and their epic. Which is one of the most basic reports I want to present to stakeholders.

            Hi heidi12,

            No hassle, but to correctly set expectations this won't be delivered this quarter. We are about to pickup the fix version field, which will unblock Releases in Next-gen projects. The remaining functionality on this ticket will follow immediately after that but this wouldn't be started in this quarter. I know that is frustrating to hear and I know this feature is half baked without it, that is why it is up next.

            Regards,
            Nathan

            Nathan Sturgess (Inactive) added a comment - Hi heidi12 , No hassle, but to correctly set expectations this won't be delivered this quarter. We are about to pickup the fix version field, which will unblock Releases in Next-gen projects. The remaining functionality on this ticket will follow immediately after that but this wouldn't be started in this quarter. I know that is frustrating to hear and I know this feature is half baked without it, that is why it is up next. Regards, Nathan

            Heidi Maul Jars added a comment - - edited

            Hi Nathan.

            Sorry to be a hassel, but do you have any idea of when the above is implemented?

            I have quite a tight deadline for making search for Issues based on an Epic work, and I just need to know if we are looking at a few weeks, a month or more. 

            I really don't feel like spending a lot of time on migration, if it will be up and running within a few weeks.

            TIA.

            Br

            Heidi Maul Jars 

            Heidi Maul Jars added a comment - - edited Hi Nathan. Sorry to be a hassel, but do you have any idea of when the above is implemented? I have quite a tight deadline for making search for Issues based on an Epic work, and I just need to know if we are looking at a few weeks, a month or more.  I really don't feel like spending a lot of time on migration, if it will be up and running within a few weeks. TIA. Br Heidi Maul Jars 

            Hi lbowers1,

            You are correct that the column is missing and I agree with you, it is frustrating. Furthermore as you stated the move operation is lossy, which is something we also need to address.

            On the 17th of May I called out:

            _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 in the list view and exported data._

            This is next up after we finish up some current Epic API work. So please hang in there a little longer.

            Regards,
            Nathan

            Nathan Sturgess (Inactive) added a comment - Hi lbowers1 , You are correct that the column is missing and I agree with you, it is frustrating. Furthermore as you stated the move operation is lossy, which is something we also need to address. On the 17th of May I called out: _That we need to solve the problem of: Finding issues for an Epic in Basic search Seeing which Epic is the parent of a given set of issues in the list view and exported data._ This is next up after we finish up some current Epic API work. So please hang in there a little longer. Regards, Nathan

            I understand that I can search for an item under a specific epic (parent) in next-gen, but the column displays incorrectly. Will this be addressed in this issue? This, and the fact that epics in classic projects lost their link is very frustrating when we migrated.

            Laura Bowers added a comment - I understand that I can search for an item under a specific epic (parent) in next-gen, but the column displays incorrectly. Will this be addressed in this issue? This, and the fact that epics in classic projects lost their link is very frustrating when we migrated.

            Hi fowler1445671014, sounds like a very frustrating day. In reply to the messaging of Next-gen projects and their functionality, I agree we could have done a better job. Getting that messaging right and clearly setting expectations has been challenging. You stated you have more advanced needs, therefore I recommend that until we offer great feature parity your needs will be best served by continuing to use Classic Jira projects.

            Hi jared1749702429, the REST API functionality is being worked on right now. Can you please email me directly about the “Field ‘parent’ does not exist or you do not have permission to view it.“? I want to look into that more.

            Regards,
            Nathan

            Nathan Sturgess (Inactive) added a comment - - edited Hi fowler1445671014 , sounds like a very frustrating day. In reply to the messaging of Next-gen projects and their functionality, I agree we could have done a better job. Getting that messaging right and clearly setting expectations has been challenging. You stated you have more advanced needs, therefore I recommend that until we offer great feature parity your needs will be best served by continuing to use Classic Jira projects. Hi jared1749702429 , the REST API functionality is being worked on right now. Can you please email me directly about the “Field ‘parent’ does not exist or you do not have permission to view it.“ ? I want to look into that more. Regards, Nathan

            HI Nathan,

            Great to see some progress on this, on some of our test instances the parent= JQL search is working as expected, others are displaying an error message "Field 'parent' does not exist or you do not have permission to view it.". This is fine I'm sure you'll get the fix out to everyone eventually!

            I'm also seeing the parent field populated in the rest API which is fantastic.

            This gives us almost everything we need to support Next Gen projects in our add-ons. The final missing piece is the ability to update the link via the REST API. It currently accepts the request but doesn't change the link. I wasn't able to find a JSWCLOUD ticket explicitly for this functionality, are you able to shed some light on this.

             

            Kind Regards,
            Jared Kells ( Easy Agile )

            Jared Kells added a comment - HI Nathan, Great to see some progress on this, on some of our test instances the parent= JQL search is working as expected, others are displaying an error message "Field 'parent' does not exist or you do not have permission to view it.". This is fine I'm sure you'll get the fix out to everyone eventually! I'm also seeing the parent field populated in the rest API which is fantastic. This gives us almost everything we need to support Next Gen projects in our add-ons. The final missing piece is the ability to update the link via the REST API. It currently accepts the request but doesn't change the link. I wasn't able to find a JSWCLOUD ticket explicitly for this functionality, are you able to shed some light on this.   Kind Regards, Jared Kells ( Easy Agile )

            Fowler added a comment - - edited

             

            Disclaimer/Warning

            Finding this issue caught me at the end of an extremely frustrating day unrelated to this. Delete if you feel it derails from the issue, but please share with someone who can do something or provide a meaningful response. 

            First, this Next Gen rollout has been an absolute joke. The people who are most eager to "pull the trigger" on a Next Gen project, are the same people who consider themselves power users. To have RUDIMENTARY omissions from early stage rollout, such as the lack of JQL querying of Epic Links, does nothing to improve my opinion of where Jira is going. Despite communications last November saying that subtasks were "hopefully on the way before the end of the year", I've held onto the idea that Next Gen provides better functionality for my team. But month after month, no meaningful features are shipped, and more and more limitations are uncovered.

            I recognize that legacy Jira is getting "long in the tooth", and as with every piece of software that is successful enough to need a "reboot", the transition will be painful. What really gets me is the poor communication about:

            1. Which features will absolutely not work or will have limited support (eg: JQL For Epic Links)
            2. When roadmap features may be released (I only learned about the subtask limited beta
              from parsing @nsturgess comment above)
            3. Who the target audience for Next Gen projects is (this has been improved recently, but too late for us)

            And this comment is nearly indecipherable, making me further question the team that I'm putting faith into solving these problems:

            So there were a small cohort of customers that were help back from the release do to some bugs, ...

            ---- 

            I WAS excited to get my team on the Next Gen project, but seemingly every week I find a new reason to regret that decision. You're burning your most devoted users and from my perspective, the near-term future is NOT looking good.

             

            Fowler added a comment - - edited   Disclaimer/Warning Finding this issue caught me at the end of an extremely frustrating day unrelated to this. Delete if you feel it derails from the issue, but please share with someone who can do something or provide a meaningful response.  First, this Next Gen rollout has been an absolute joke. The people who are most eager to "pull the trigger" on a Next Gen project, are the same people who consider themselves power users. To have RUDIMENTARY omissions from early stage rollout, such as the lack of JQL querying of Epic Links, does nothing to improve my opinion of where Jira is going. Despite communications last November saying that subtasks were "hopefully on the way before the end of the year", I've held onto the idea that Next Gen provides better functionality for my team. But month after month, no meaningful features are shipped, and more and more limitations are uncovered. I recognize that legacy Jira is getting "long in the tooth", and as with every piece of software that is successful enough to need a "reboot", the transition will be painful. What really gets me is the poor communication about: Which features will absolutely not work or will have limited support (eg: JQL For Epic Links) When roadmap features may be released (I only learned about the subtask limited beta from parsing @nsturgess comment above) Who the target audience for Next Gen projects is (this has been improved recently, but too late for us) And this comment is nearly indecipherable, making me further question the team that I'm putting faith into solving these problems: So there were a small cohort of customers that were help back from the release do to some bugs, ... ----  I WAS excited to get my team on the Next Gen project, but seemingly every week I find a new reason to regret that decision. You're burning your most devoted users and from my perspective, the near-term future is NOT looking good.  

            Hi brandon32,

            So there were a small cohort of customers that were held back from the release due to some bugs, there is a chance that you might be in that cohort. But first, can you go into Project settings->Issue types. If there is no Subtask issue type can you please click "+ Add issue type". You should should see Subtask as an issue type there.

            If you could me know the outcome please, probably best to email me direct at nsturgess at atlassian dot com.

            Regards,
            Nathan

            Nathan Sturgess (Inactive) added a comment - - edited Hi brandon32 , So there were a small cohort of customers that were held back from the release due to some bugs, there is a chance that you might be in that cohort. But first, can you go into Project settings->Issue types. If there is no Subtask issue type can you please click "+ Add issue type". You should should see Subtask as an issue type there. If you could me know the outcome please, probably best to email me direct at nsturgess at atlassian dot com. Regards, Nathan

            Brandon Hite added a comment - - edited

            Hi Nathan, unfortunately it looks like our team isn't part of the "majority of customers" that have sub-tasks and parent/epic link JQL search functionality. Is this a bug or are we just part of the latter rollout phase?

             

            EDIT: I lied! I wasn't trying "parent", but "parent link". "Epic link" still doesn't work, but I'm able to get the job done just using "parent" so no complaints from me! I don't see a subtask option to toggle in the Features settings, so if those are supposed to be intertwined, I am missing that.

            Brandon Hite added a comment - - edited Hi Nathan, unfortunately it looks like our team isn't part of the "majority of customers" that have sub-tasks and parent/epic link JQL search functionality. Is this a bug or are we just part of the latter rollout phase?   EDIT: I lied! I wasn't trying "parent", but "parent link". "Epic link" still doesn't work, but I'm able to get the job done just using "parent" so no complaints from me! I don't see a subtask option to toggle in the Features settings, so if those are supposed to be intertwined, I am missing that.

            Just an FYI, Nate has 15 other issues currently assigned

            I can relate! Sole developer on my current board and 30+ issues with a client deadline looming! Positive vibes @ Nate and all the Sub-task devs!! I bet it feels good to be breaking the back of the sub-tasks and parent issues challenge though, well played!

            I'm sure I speak for alot of the followers here when I say thanks again for persevering with this work!

            Not only that, I'm positive my managers (and clock watchers) will all thank you when the Basic field and parent column comes into play, then they can do their reports and beat down on my shoulders as they see their epics growing instead of shrinking! haha

            Just customizable workflows and parallel sprints (the 2 bigguns for me) and we'll really be able to get smashing with Next Gen

                

            Dan Walker added a comment - Just an FYI, Nate has 15 other issues currently assigned I can relate! Sole developer on my current board and 30+ issues with a client deadline looming! Positive vibes @ Nate and all the Sub-task devs!! I bet it feels good to be breaking the back of the sub-tasks and parent issues challenge though, well played! I'm sure I speak for alot of the followers here when I say thanks again for persevering with this work! Not only that, I'm positive my managers (and clock watchers) will all thank you when the Basic field and parent column comes into play, then they can do their reports and beat down on my shoulders as they see their epics growing instead of shrinking! haha Just customizable workflows and parallel sprints (the 2 bigguns for me) and we'll really be able to get smashing with Next Gen      

            Just an FYI, Nate has 15 other issues currently assigned

             

            Deleted Account (Inactive) added a comment - Just an FYI, Nate has 15 other issues currently assigned  

            dan291554704 firstly I would like to make an apology for the basic JQL not being in there now. But yes you are correct, it is coming and we are about to start work on it.

            Again sorry for taking so long for to get you the OR to allow you to query Next-gen Epics, that ability was part of the subtasks feature, which took a lot longer than expected due to different complications that came up when developing the feature. I don't take offence at all, I actually agree with you, actually we all do internally. We all have been super eager to rollout for sometime.

            Nathan Sturgess (Inactive) added a comment - dan291554704 firstly I would like to make an apology for the basic JQL not being in there now. But yes you are correct, it is coming and we are about to start work on it. Again sorry for taking so long for to get you the OR to allow you to query Next-gen Epics, that ability was part of the subtasks feature, which took a lot longer than expected due to different complications that came up when developing the feature. I don't take offence at all, I actually agree with you, actually we all do internally. We all have been super eager to rollout for sometime.

            Dan Walker added a comment - - edited

            Thanks for the update Nate!

            Do I read that "subsequent work" part correct in that the basic field (dropdown) will also work some time in the future? That would be cool!

            Update :

            I know tickets can often be very demotive so in order to inject some positivity and feedback thought I'd try the parent field out in JSQL... and it works a treat!

            project = PKEY AND issuetype in (Bug, Change, Task) AND parent = )PKEY-2 ORDER BY created DESC

            Worked perfectly in our next gen! Thanks for all your work, look forward to the subsequent developments.

             

            PS> There's a joke in there somewhere about being "Better Nate than never!" but please don't take this as a whine about how long its taken, it's just some light whimsy!

            Dan Walker added a comment - - edited Thanks for the update Nate! Do I read that "subsequent work" part correct in that the basic field (dropdown) will also work some time in the future? That would be cool! Update : I know tickets can often be very demotive so in order to inject some positivity and feedback thought I'd try the parent field out in JSQL... and it works a treat! project = PKEY AND issuetype in (Bug, Change, Task) AND parent = )PKEY-2 ORDER BY created DESC Worked perfectly in our next gen! Thanks for all your work, look forward to the subsequent developments.   PS> There's a joke in there somewhere about being "Better Nate than never!" but please don't take this as a whine about how long its taken, it's just some light whimsy!

            Hi guys,

            The majority of customer should now have Subtasks in their Next-gen projects. If you can see subtasks in your Next-gen project settings then this means that 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:

            • Epic suggestions in Basic and Advanced JQL search
            • Parent data in the Issue List View and in exported data

            Regards,
            Nate

            Nathan Sturgess (Inactive) added a comment - Hi guys, The majority of customer should now have Subtasks in their Next-gen projects. If you can see subtasks in your Next-gen project settings then this means that 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: Epic suggestions in Basic and Advanced JQL search Parent data in the Issue List View and in exported data Regards, Nate

            Matt Cox added a comment -

            Hi Nathan.  Can you give us some kind of update on when this is targeted for release? There are a lot of people hanging out for this crucial feature. Last response from you was on 16th May. Thanks.

            Matt Cox added a comment - Hi Nathan.  Can you give us some kind of update on when this is targeted for release? There are a lot of people hanging out for this crucial feature. Last response from you was on 16th May. Thanks.

            Kyle Lear added a comment -

            +1 

            This is breaking my reporting in confluence using next gen 

            Kyle Lear added a comment - +1  This is breaking my reporting in confluence using next gen 

            Very critical issue for us; makes Epics more or less useless if we cannot query for them. I see them on the Roadmap but that feature isn't ready for prime time yet.

            Deleted Account (Inactive) added a comment - Very critical issue for us; makes Epics more or less useless if we cannot query for them. I see them on the Roadmap but that feature isn't ready for prime time yet.

            Nick Jones added a comment -

            Loving the simplicity and self service of the next gen projects, thanks. 

            We want to surface next gen epics, user stories, and tasks into Confluence using macros. Currently even the basis Jira issues macro doesn't work, due to this issue with Epic link not being in place.  

            Nick Jones added a comment - Loving the simplicity and self service of the next gen projects, thanks.  We want to surface next gen epics, user stories, and tasks into Confluence using macros. Currently even the basis Jira issues macro doesn't work, due to this issue with Epic link not being in place.  

             We very much want this as we have migrated from classic to next-gen projects and need to search by epic for reporting purposes

            Laura Bowers added a comment -  We very much want this as we have migrated from classic to next-gen projects and need to search by epic for reporting purposes

            HI there; I see this in progress; when is it coming?

            Lia Schiza added a comment - HI there; I see this in progress; when is it coming?

            +1

            David Raffelt added a comment - +1

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

            Дмитрий Луценко added a comment - Need to search for issues by epic and epic by issues.

            Larry added a comment -

            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.

            Larry added a comment - 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

            Nathan Sturgess (Inactive) added a comment - 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: Finding issues for an Epic in Basic search 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

            Dan Walker added a comment -

            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....

            Dan Walker added a comment - 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....

            Dan Walker added a comment - - edited

            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...

            Dan Walker added a comment - - edited 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...

            Eric Wyman added a comment -

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

             

            (I tried creating a subtask, lol)

            Eric Wyman added a comment - Hahaha. Thanks, it's my first day using Jira   (I tried creating a subtask, lol)

            Dan Walker added a comment -

            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

            Dan Walker added a comment - 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

            Eric Wyman added a comment - - edited

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

            Thanks

            Eric Wyman added a comment - - edited Can you please provide a link to where you would like the ticket entered? @nsturgess Thanks

            Dan Walker added a comment -

            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.

            Dan Walker added a comment - 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.

            Indrek Petti added a comment - - edited

            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?

            Indrek Petti added a comment - - edited 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

            Nathan Sturgess (Inactive) added a comment - 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

            Nathan Sturgess (Inactive) added a comment - 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

            Eric Wyman added a comment -

            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. 

            Eric Wyman added a comment - 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.

            Marco Centin added a comment - 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.

            Dan Walker added a comment -

            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)?

             

             

            Dan Walker added a comment - 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>
            

            Nathan Sturgess (Inactive) added a comment - - edited 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!

            Deleted Account (Inactive) added a comment - 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

            Dwight Pfundstein added a comment - 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.

            Daniel Nordmark added a comment - 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!!

            Scott Bailey added a comment - @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!!

            Dan Walker added a comment -

            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>

            Dan Walker added a comment - 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>

            Mike Heyns added a comment -

            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!

            Mike Heyns added a comment - 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.

            Jason.Creak added a comment - 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.

            Missy Ann Mathews added a comment - 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.

            Ben Jackson added a comment - - edited

            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.

            Ben Jackson added a comment - - edited 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 

            Jason.Creak added a comment - 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 

            Dan Walker added a comment -

            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!

            Dan Walker added a comment - 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?

            Scott Fedorov added a comment - 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.

             

            Deleted Account (Inactive) added a comment - 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?

            Michael Trice added a comment - 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

            Nathan Sturgess (Inactive) added a comment - 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.

            Michael Trice added a comment - 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.

            Jason.Creak added a comment - 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.

            Philippe Jung added a comment - 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?

            Deleted Account (Inactive) added a comment - 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.

            Missy Ann Mathews added a comment - 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...

            Indrek Petti added a comment - 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.

            Rudiger Wolf added a comment - 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. 

            Scott Fedorov added a comment - 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.

            Rudiger Wolf added a comment - 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.

            Greg Sarcona added a comment - parentEpic() doesn't work either.

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

            Richard Hohl added a comment -  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 added a comment - @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.

            Dan Walker added a comment -

            @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.

            Dan Walker added a comment - @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.

            Emily Spitzer added a comment - 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.

             

            Santiago Sanchez added a comment - 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. 

            Courtney Arnott added a comment - 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" ?

            Dan Walker added a comment - Is this the very definition of an "Epic Fail" ?

            jj added a comment -

            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. 

            jj added a comment - 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. 

            Dan Walker added a comment -

            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

             

             

            Dan Walker added a comment - 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,

            We use the 'Jira issue/filter' macro in Confluence to create release notes of Stories related to specific Epics which, after creating an export, we share with external partners to indicate status of projects.

            Thanks for picking this up!

            Pim Meeuwesen added a comment - Hi Nathan, We use the 'Jira issue/filter' macro in Confluence to create release notes of Stories related to specific Epics which, after creating an export, we share with external partners to indicate status of projects. Thanks for picking this up!

            Barry added a comment -

            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

            Barry added a comment - 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

            Phil added a comment -

            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.

             

            Phil added a comment - 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.

            Deleted Account (Inactive) added a comment - 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

            Marcel Herrmann [APTIS] added a comment - 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

            Rossana Badiali added a comment - 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.

            Stef Spijkerman added a comment - 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

            Indrek private added a comment - 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

            Indrek private added a comment - 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.

             

            Ibrahim Khan added a comment - 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.

            Aubrey Kotelko added a comment - 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.). 

            Daniel Naumann added a comment - 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

            Nathan Sturgess (Inactive) added a comment - 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

            Dan Walker added a comment - 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.

            Dave Mahoney added a comment - 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

            Deleted Account (Inactive) added a comment - 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.

            Joerg Palluch added a comment - 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.

            Allyson Gallant added a comment - 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

            Courtney Arnott added a comment - 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. 

            Courtney Arnott added a comment - 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.

            Scott Bailey added a comment - 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.

            Mike Heyns added a comment - 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

            Philippe Jung added a comment - Extremely important issue

            Agree with others, please implement this feature.

            Craig Kumick added a comment - 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.

            Bobby Smith added a comment - 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.

              nsturgess Nathan Sturgess (Inactive)
              dbraun@atlassian.com Douglas B (Inactive)
              Votes:
              602 Vote for this issue
              Watchers:
              306 Start watching this issue

                Created:
                Updated:
                Resolved: