Please reopen and add support for timesheet functions.

Can you please reopen, as we need Tempo reports to list Project > Epic > Issue > Sub-Task, see problem description here https://community.atlassian.com/t5/Jira-Software-questions/Tempo-report-doesn-t-show-Epics/qaq-p/1597821

Following for need Epic/Parent Name in the query results for macro in confluence.  it just shows key which is not helpful. like  in JQL results it shows parent name. 

I am able to pull the Epic/Parent name in the query but it only exports the Key.  Is there not a way to export the name also?  I could do this before moving to NextGen.  

Hi guys!

It looks like there is no real workaround apart from getting the child issues of the epic and then searching for subtasks of stories in the epic. And this solution only works for some one-off use cases.

If you need full support for Epic->Story->Subtask hierarchies, consider our professional paid indexing service JQL Search Extensions for Jira Cloud.

After you install the app you can get all issues under your epics:

issue in childrenOfIssuesInQueryRecursive("key in (EPIC-1, EPIC-2)")

I hope it's of help to at least some of you!

I have exactly the same problem with sub-tasks and it is driving me slightly mad.

We have now had to ask the team to never log time under sub-tasks, otherwise it is time that just disappears.

Quite frankly the issues with the changes to Epics and parents for next gen projects is baffling.

Hi @Nathan Sturgess,

Above solution works and it pulls only the Story, Task and Bugs under the epic but not the subtasks under the story.

Actually I am trying to use the JQL in Tempo for Logged Time Report. In Classic Software project Filter by Epic works like a charm but since we moved to Next Gen project Filter by Epic is not working. As alternate solution I am trying to use JQL whereas the query appears as below. Problem here is, report pulls all the time logged under Story, Task and Bug issue types but the time logged under "subtasks" are not getting accounted.

JQL: project = ER AND parent in (ER-2)
ER-2 is the Epic
  ER-3 - Story 1
    ER-4 - Sub Task 1
    ER-5 - Sub Task 2

 ER-6 - Story 2
   ER-7 - Sub Task 1
   ER-8 - Sub Task 2

What I am looking for?: My JQL should pull all the Story under Epic "ER-2" along with subtasks so that I can use the JQL in Tempo

Took me forever to find this answer. Thankfully, it worked. 

That's worked.  Thanks @Nathan Sturgess

Hi karen5,

Sorry for the inconvenience this has caused you, the bug has been triaged to be fixed.

In the meantime there is a workout here: https://jira.atlassian.com/browse/JRACLOUD-74373

Regards,
Nate

https://jira.atlassian.com/browse/JSWCLOUD-17239?focusedCommentId=2327488&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2327488

Is there any update on this?  I am getting the same issue when I attempt to filter issues in a project by 'parent'.

Field 'parent' does not exist or you do not have permission to view it.

My JQL is as follows

project = MyProject AND parent = MyProject-163 ORDER BY created DESC

Forgive me, I see there is a new field called "Parent" and I can use that in my JQL fields.  I'm glad this is implemented. 

Hi akshat6 I have found the owner. Can you please email me directly nsturgess at atlassian dot com so that I can find out more info from you please?

9fe4e369cb27 if you can please go to https://support.atlassian.com/, we can get someone to look into that for you.

@Nathan Sturgress, I can't use 'parent' field in my next gen project, shows 'Field 'parent' does not exist or you do not have permission to view it.' error. The other two fields (parentEpic and "Parent Link") don't work. Suggestions?

akshat6 still chasing that up who owns that and finding out more info about the macro, just email me directly about it please so that it is not noisy here on this ticket. Thanks and Merry Christmas!

@Nathan Sturgess Thanks for the quick turnaround ! I was interested in getting the parent summary in the JIRA Issue/Filter macro in Confluence, and assumed it would be implemented along with the export feature. This still seems to be not possible right now, so would this be a quick fix too?

akshat6 We are rolling it out now, if you can't see it, you should see it shortly. After that please find your requested column in the exported file 🙂.

christoph67 good point! Let me go look into that for you.

johan.b.brodin yeah good question, we have discussed having something like decedentsOf = for any level of hierarchy (which means in theory would include a level above Epic). This was an internal request from another team but have not heard anything further to be honest.

Is there any plans to support an easy JQL query to get all issues in the Epics including those issues subtasks? So the complete issue tree sitting below the epic. Could be something like parentAll = "EPIC-1"

In Jira using JQL 'Parent' shows the 'Summary' of the parent, which is great.  However, in Confluence using JIRA Issue/Filter 'Parent' shows the 'Key' of the parent.  Bug?

indrek5 Please ping me on nsturgess at Atlassian dot com thanks

I would love to as a next step to be able to use Automation for Jira scripts support assigning stories to epics (parents) in next gen. Manually assigning automatically created stories to parents is such a stupid hassle. Any insights- has this been under consideration, Nathan?

0f2016f08d2b Classic Epics above are from Classic Projects (not next-gen) so they don't have a parent id.

Not via official API but there is enough information in Jira to use NextGet as if they were Software projects for many use cases. We have succeeded with this approach and support Epic Links for NexGent projects in our Links Hierarchy app from all the views (tree, graphs, matrixes).

The resultset displayed for the JQL does not include parent-id in the specified column. Please check this.

@Nathen Sturgess, 

I don't know if your comment might have got lost but I' like to extend my appreciation for persevering with this and rolling it out! Thanks!!

I hope the community will also appreciate your efforts also!!!

They do say the longest jobs yield the most satisfaction so kudos to you for all your effort, I'm glad you stayed focused on productivity while everyone else seems to have been pre-occupied changing the menu's and tampering with the look and feel (IHMO Wasn't broke, why tamper with it!).

Don't suppose I can convince you to go for a double and resolve the darned "Parallel Sprints don't work in Next Gen" (JSWCLOUD-17195) issue too???? You may become the saviour of many an Agile Jira team!!! haha

Merry Christmas to all you guys at Atlassian and everyone in the Jira community!!!! 

@Andrea Della Corte,

There's history in the channel comments, but it boils down to "Epic's are different in Next Gen". Don't ask me why, They where fine the way they where IMHO but Atlassian decided that was too complex for next gen, hardened them and now we have this bastardisation with a mix of `parent` and `Epic Link` for old and new....

Jira portfolio already defined a parent link field, why not name the one for next-gen the same way?

Please make this field to be supported also in Jira Cloud for Sheets fields list. Currently it lets me pick it but the outcome is error saying that the field is not supported:

Agree with @Mike Stewart and @Noel Salt on the usefulness of the Epic summary in exports and when adding a table of issues on confluence. @Nathan Sturgess could we have a link to that ticket you just created?

Hi,

We didn’t export summary because it doesn't have the same character limit like Epic Link does and Jira doesn’t support importing a parent by its summary.

I have just opened a ticket to add Summary to the export (and keep the id) this way it will be more readable whilst still allowing import via the id. The work is fairly trivial so shouldn't be long. Thanks for the feedback mike.stewart and 8eb427be466b.

Regards,
Nate

Hi. The text description (rather than ID) when exporting would be very useful for reporting purposes.

Issues list shows the EPIC Summary description text now in the Parent field. But wen exporting an issues list to CSV the numerical ID for the EPIC is given (not the text description). Is there a way to get the text description to come through in an exported list? Thanks.

Hi guys, we had a bit of a delay but this is now fully rolled out.

You are now able to select the Parent column in the Global Issue Navigator and have the parent information show in the exported file.

Regards,
Nate

As Jason said!

Happy Birthday JSWCLOUD-17239!  

Despite Nathan's best efforts to nurture this problem child, Next Gen definitely seems to be suffering from Gen X issues. After a year of effort Next gen continues to struggle to grown up and gain the functionality and flexibility of an Agile system, like its predecessors the classic project. Failing to look up to it's peers it seems more focused the last year on changing its look and standing out, despite the fact that many people are at odds with how it's dressed itself, and how this new look has itself caused issues like creating linked issues from one project to another.

Here's hoping this year some maturity emerges in the Next Gen project, Epics start to resolve in a decent manner, parallel sprinting returns (JSWCLOUD-17195 ), custom workflow support (JSWCLOUD-17434 ) (to name just a couple) and grows into a nice responsible platform that can support various scales of enterprise instead of the junior school, entry level Agile/Kanban it seems to be currently....

Happy Birthday and here's to your future, we all wish you well and just remember we are all behind you!

/me creates classic project

Hi dave1406477931,

Just a heads up, there is a way to tell the difference between next-gen and classic projects.
https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-project-projectIdOrKey-get
There is a style property

Regards,
Nathan

Happy Birthday @JSWCLOUD-17239 !!     How has your first year Unresolved been?  Its definitely been a long one for us, putting off all our dreams for using NextGen. 

The "parent=" rollout of 10-Sep (thanks Nathan!) isnt really very useful in practice without the rest of this (and JSWCLOUD-17479)

I really fear for the life of your real parent (Atlassian) if this takes a year or more to get done.   Hopefully NextGen is working better for market expansion than the public beta bit...... 

Thanks for the response Dave. It sounds like this is an Atlassian issue, then.

Sorry for the delay, Kyle. 

Unfortunately Atlassian don't provide a way to prevent showing a side-bar item based on whether the project is nextgen or not. We can only tell whether it is a software project or not, not next-gen or classic. 

The good news is that we are starting work on support for next-gen projects today as we believe all of the APIs we require are now live.

Thanks

~Dave Elkan

Co-CEO, Easy Agile

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.

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.

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.

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

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

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

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 )

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.

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

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

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.

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

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.

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

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

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

+1

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?