Awesome news,
Email sent. looking forward to it. 

Perfect Eoin!

You've got mail 2x for two hostnames.

That's good news! Thanks for your hard work!

Thanks so much for the update!

Thank you so much, already sent the email.

Thanks so much Eoin! That's great news!! Please give my regards to the developers and their hard work. I'm imagining lots of long nights and weekends, and I know what kin of sacrifices have to be made because of that

And one for me please, BTW Hallo Mads  

Hi Eoin,

This is fantastic news. Thanks for the update.

You've got mail  

Thanks all for you patience. I understand it has been frustrating and I can assure you there are multiple people working on getting this first iteration of subtasks ready. The large scale nature of the architecture changes has been challenging (although will ultimately be rewarding in the long term) and has reduced our ability to provide you with accurate timing on when subtasks will be available. There has been no intention to mislead and every update has been with the full information that we have at hand. The team here are as excited as you to having this first iteration ready for use and will be looking to make improvements as we receive your feedback.
For those of you that would like to be part of the first cohort of instances that we enable subtasks on; can you send an email to eryan@atlassian.com with your hostname (e.g. xx.atlassian.net) in the body and with "Next-gen Subtasks" as the subject? I will subsequently reply to your email at the point we turn on the feature flag for your instance (and I'll also post a general update here on this ticket for transparency)
As of now, we have just merged changes to resolve the last known outstanding blockers - one is a performance fix and we will need to verify the impact of this fix tomorrow in staging. All going well with this fix, we will begin the roll-out once the change gets pushed to production.

I do find it ironic that Next gen was released as a MVP (Minimum Viable Product) yet this essential feature is being held back.  It sounds like this is is also MVP due to the latency, but you released Next Gen like that, so why can't we have this now?

Hi Michael,

I'm using Firefox 66.0.2 (64bits) under Windows 10 and have no issues with the comment button.

As for the sub-tasks issue, I was quite surprised to not have it from the beginning as it seems for me an essential element for any project management. So, my 5 cents to the request to implement it asap and to have some feedback from the development team, as the absence of communication may be distructive by itself.

Even I'm gonna have to ask for an update, Eoin. I'm sure you guys are extremely busy and getting inundated with requests like this doesn't help, but eventually stuff has to give, ya know? :/

Also, FWIW, is anyone else having trouble clicking the comment button in firefox? I can only actually see it in Chrome.

I am sure that everyone on this thread would appreciate a word from the Jira team on the timeline and why the commitment keeps getting missed. Can someone please give an update?

@Tom, if I were you, I'd ask your Jira admin to move your Next Gen projects into a Jira classic project and manage separate boards for your clients.
As I'm sure you appreciate, Jira is an industry standard tool so I'd advise you to "roll with the punches".
If you really want to shift to an alternative tool, the only one I'd recommend is Visual Studio Team Services (now known as Azure DevOps)[ https://azure.microsoft.com/en-gb/services/devops/boards

...but please be aware of the steep learning curve and licence costs.

Do you know any good Jira alternatives? Something with roadmap, easy to use backlog/sprint board, basic metrics AND SUBTASKS?  I have multiple clients using Jira next gen due to simple to use interface, but the lack of subtasks (and updates on clarity when can we expect them) has finally killed their patience.

Same here - was loving the next-gen UI, but no sub-tasks and epic link not working in JQL are massive drawbacks. I don't think I'll be using it for another next project until these issues are addressed. 

We're in the same position, I would rather have 300ms response time than not having sub-tasks. We're not in the position of having to migrate back to classic, which means we'll probably never go back to Next-Gen - it's too much work to be migrating back and forth when we have projects to run.

+1 on Gary's idea, I love the idea of a switch. Granted, I do understand that that may not be trivial given the current point in development time.

At this point I'm trying to be as patient as I can, as I know how these things go sometimes. However, the lack of subtasks is now starting to affect the metrics that go to the project management and my higher ups, and without that kind of relationship the metrics are skewed and have to be tweaked manually. The way Jira handles subtasks is one of my favorite aspects of the application, and I have no intention of going anywhere else. All I can do is implore you all to provide more status updates on where things stand. I see a lot of attrition ahead without this feature. Thanks all!!

This is starting to become an issue for our company as well.  I am glad it is being worked on, also glad we got an update on the 22nd March (which is only a little over 7 days ago).  Patiently waiting for another update some time this week (which would qualify as "next week" from the original post - at least in my book).

As far as the board load time - make it a switch.  If you want sub-tasks, and use them, put up with the additional board load time.  You can optimise it later and give us all a surprise present in a future release.

Other than that, really liking the next gen board.

Eoin - Understand you don’t want to compromise on performance, but you’ve got a number of folks who are going to leave Next Gen (or JIRA) who are telling you they’d prefer a slower implementation with tasks than no tasks at all.  It’s worth considering.

If you’re not the person who decides how many resources to apply to this problem, I recommend sharing the feedback with whomever can make this a higher priority problem to fix.

I am not considering switching to classic projects, I want to find an alternative to Jira altogether. This whole experience has left a really bad taste in my mouth. Subtasks and queryable Epic links would keep me here, or at the very least consistent communication with us and actual timelines, but it looks like there is a single developer working part time on Next Gens, so I don't see any significant progress being made. Out of the dozens of future enhancements listed here there are only TWO that are In Progress. Seems like Atlassian has abandoned next gens?

I am just beyond words.

Echoing previous comments, my engineering team is at the breaking point not having sub-tasks. If something is not released this week we'll be forced to switching back to Classic. Not too thrilled about that.

Releasing the feature with 300ms lag time to test functionality and incrementally improving that time makes sense to me!

Hi Eoin,

Please be consistent with your updates; even if it's 10s to write - "still heads down working."

You said clearly on 3.22 "Apologies for the delay (although we don't expect this to be a big delay) and I'll update again next week when I have more info."

That next week came and went.

Eagerly awaiting sub-tasks...

Hi Eoin,

Thanks for the last answer.
A week more has passed since your last update.

Could you give brief update on where you are in regard to this feature?

Please note that the "Sub-tasks are coming soon!" fancy notice was added on Nov 28th, almost 4 months now. And the ticket was moved to "In progress" on Jan 23rd, more than two months now......

Furthermore, this ticket JSWCLOUD-17155 is the subtask #41 out of 123 subtasks of JSWCLOUD-17392, which is a ticket of type "Suggestion". Is this the way to use your tool?

^^ Agreed.

Any update on this? I would rather take a 300ms delay on the boards than the multi-minute delay incurred by the clumsy sub-task workarounds I've come up with to use during our planning and grooming meetings.

I jumped straight into the next-gen project type when I got a new job managing a tech department last year, with the understanding that this was what Atlassian's wanted people to use going forward, and I feel really stuck now because basic functionality is missing, and there have barely been any significant updates in 2019. Migrating to classic would be a very disruptive and traumatic thing for my team.

Read many of comments for this and other feature threads and think you guys are better people than me.  My position is sub-task is a core feature and should've been included in the first batch.  Atlassian, this is what you do!  This service is not free.  Seriously, get your shit together and get this out already.

^^ Agreed.

Performance is not to be understated but we do not have a simple work around for this and its caused us to abandon use of next generation projects.  I would prefer to see it functional and deal with the 300ms now versus a future promise.  It won't impact any of our project setup or day to day us.  It will only get slightly faster in a non functional way.

Thank you so much for looking in to that, Eoin and crew!! It's worth the wait to have a performant system, as something super slow would slow down development as a whole.

I also want to give a big thank you to all of the team working on this, as well as yourself, Eoin, for keeping us updated as much as possible. There are definitely going to be some angry folks out there, and I can understand that, but from my perspective on something like this, an MVP isn't quite gonna work out, so we need to wait for something more fleshed out. The fact you all are taking the time to do this is fantastic, and I'm sure the devs are putting in a ton of extra work to make it all happen. It's extremely appreciated, the sense of urgency put in to making this happen. By now I know you all know how important this feature is to the lot of us, so reiterating that won't help. Major props to you all for putting up with the anger and frustration, and being up front enough to actually explain the delays themselves. Great job guys!!

All, with subtasks switched on we've seen a decrease in performance for the board load (about an additional 300ms on average). We're currently looking at ways to decrease / negate this additional time. Performance is a critical factor for us with next-gen and it isn't something we want to compromise on. Apologies for the delay (although we don't expect this to be a big delay) and I'll update again next week when I have more info.
Thanks

@Eoin - This will be super helpful for my organization moving forward! Completely understand the complexities and looking forward to the release. The beauty of Next-Gen that I feel a lot of people miss is that it enforces Agile practices among users. Right now, it's the perfect PM tool for well crafted stories. However, without sub-tasks inter-team tracking is difficult.

In terms of swimlanes, those will be incredibly helpful for our developers. Our stories are well understood and pointed but our developers have resorted to using Trello to keep track of subtasks associated to their story. As the PM, I'm not a task manager nor do I want to be. But wearing my SCRUM hat, the team needs to be able to effectively see where things are on a day to day basis which is where this will play into.

On top of that being able to tie Git commits back to subtasks gives our engineers more granularity and a tighter audit trail. An example of a subtask may be implementing design changes which would be one commit while another subtask is adding a new button function under the hood and likewise another commit. 

mads.donkin and all, we had hoped to start rolling out early next week but we have hit an issue. We're currently gathering information on the potential impact and will then decide on a resolution. Our thoughts right now are that this will push us out another week.
The issue occurs where users are including next-gen issues in scrum classic boards with active sprints (using JQL). The way we have rearchitected the board on next-gen means that there is a possibility that the board in the next-gen project will fail to load in this scenario.
I'll keep you updated.

Hi Eoin,
Now it's a few weeks later

Where are we in terms of ETA on this feature?

Thanks,

Mads

Thanks for the update Eoin! Sounds like a great technical direction for Jira, granted as a user/customer I do wish subtasks had taken priority, but as a dev I think infrastructure is more important than folks know, so I'm elated to hear that.

Looking forward to more news!

Thanks!

All, to give you all an update - we hit far more technical obstacles with subtasks than we had originally envisioned. As some of you know, we are moving to a microservices architecture and introducing a raft of new technologies as part of the new Jira. The good news is we are very close and should have subtasks available within the issue view within the next few weeks, followed soon after by the ability to track subtasks on the board by enabling swimlanes on the board.
I'm keen to learn more about who uses the swimlanes in your team to track subtasks and in what you would like to see in the swimlane header. If you're free for a 15 min chat, I'd like to show you mockups and ask you some quick questions... https://calendly.com/eoinryan/15min
Thanks

Hi chris154 - sorry for the silence. Will follow up on the loop flow you are having with bug create.
Thanks for the feedback on the issue view - we'll be looking to iterate on the issue view over the coming months so this is invaluable. A quick point on the comments/history/work log section - you can paste images in the comments box.

Hey Eoin,

You've all gone quiet on this issue. Any updates at all? It would be nice to here something.

I'm sure you are working very hard on this issue. It's just hard on the other side when we are completely in the dark.

Please don't take this as a criticism though.

100%!

This is an urgent matter, should be the top 1 priority of the upcoming features

Eoin,

A cool site indeed

No, I wasn't working at the White House!!!

I was working in a school in Melbourne Australia and I was responsible for introducing the first computer (an Apple II of course) into the school. I pretty much had access to it whenever I wanted!!

Enough of that though (interesting as it is).

I'm finding a few issues at the moment that are not first order issues but I wanted to report them so they are recorded.

I went to report what I thought was a bug in the New Jira Issue view. If I click "Create" here, it asks me if I want to create a suggestion or a bug. If I choose 'bug' it says I have to use Atlassian's bug reporting system (I can't remember the exact words) but when I click OK, it takes me right back to the support front page. If I select "Suggestions and bug reports" it goes in the same loop again. (I know this is not a Next-Gen issue but I seem to have no where else to report it.)

With regard to Next-Gen:

1. I am finding the documentation for new features quite confusing. In particular for the New Jira Issue View. I really can't follow it and I don't really understand what I am supposed to be seeing. (I'm referring to the documentation in the blog.)
2. When I go to comments in this new view, it says I can choose "History or Worklog". If I choose worklog. I'd like to paste a screenshot here but there doesn't seem to be anywhere I can do that in a comment. However it basically gives me a table with headings "Field", "Original Value" and "New Value". Not very readable.
3. When you "Log Work", the 'Comments" section is no longer "docked", we have to scroll past the "Tempo" section to get to comments.

That's about it for now.

Oh, just one last thing. How do I "mention" you here? I tried "User mention" but it doesn't seem to work.

Did someone say computer history? I thin Atlassian is trying to distract us with cool stuff

Would this be a good place to mention that I'm unable to see the comment button in firefox and only in Chrome? Thanks so much for the engagement, from my side it's wonderfully appreciated!

Thanks chris154 and mlawson for taking the time to provide feedback and suggestions!! I can tell you we're also very excited about next-gen. chris154 I found this cool site on computer history... https://www.computerhistory.org/timeline/1978/ - I see the first entry is that computers were first installed in the White House in 1978 - is this where you had your first computer?

Hi Eoin,

I can't tell you great that is to hear.

We know you guys are working really hard on next-gen and I, for one, am really excited about it. That's why I jumped on board. (I am unashamedly, an early adopter. I had my first computer in 1978 and my first mobile phone in 1991.)

Like Michael, I will be signing up as soon as I have posted this comment.

You guys are doing a great job. We only have to look at the history of Atlassian to know you will continue the great tradition.

Thanks so much, I really appreciate these and will be signing up for them after I hit the "add" button. I have full faith you guys are working to iron these processes out, and look forward to the future!!

Hi mlawson chris154. Thanks for the feedback. We're always looking to improve so we'll look at what we can do here with feedback. I'll go through some of the things we do and some changes we will make.

• Version numbers won't easily work - we have a significant number of engineers making changes right across the Jira code base in parallel, and we are deploying to production more than once a day. The version number is actually visible in the About Jira modal under Help in the navigation menu - it's a hash though and not sequential so you won't get much from this.
• We've been using a Next-gen group community to keep users updated... https://community.atlassian.com/t5/Next-gen/ct-p/agility... but we've not been active enough on here in the past couple of months. We'll look to update/create a new article on here which highlights the changes we are making, and work harder at keeping this updated.
• Similarly we trialled a public roadmap for next-gen... https://www.atlassian.com/roadmap/jira-software... but again we haven't been active enough. We'll also get this updated.
• There is a monthly email newsletter that goes out to technical contacts of instances that have a next-gen project that does a wrap of changes in the previous month. We are looking at how we can improve the targeting of that email int he future, but we have some limitations preventing that right now
• Finally there is are weekly release notes blogs, linked using the What's New link in the Help navigation menu item. This is driven by feature flags within the product and with some manual intervention from our team. Here is the direct link to the last blog... https://confluence.atlassian.com/cloud/blog/2019/01/atlassian-cloud-changes-jan-7-to-jan-14-2019#AtlassianCloudchangesJan7toJan14,2019-jira.software Again this doesn't seem to be capturing everything so we'll look to tweak this process.

Keen to hear your thoughts on these ways we communicate out and whether you have any other suggestions on how we can improve. (My email address is eryan@atlassian.com if you wanted to reach out directly or I'll see the reply on here as well)

Well said Michael.

Hi Eoin,

Thanks so much for the update!! Good things take time, and I'd never want to see something this awesome go out the door unfinished, dev to dev it totally happens. To chime in with the above, I also think there should be a few more updates on major features like this, but otherwise I completely understand that delays happen. In our case, it's trying to show higher ups that cloud is better than the Jira 5 instance we were hosting locally, and in my opinion it definitely is, it just gets harder to show when we don't have solid ways of doing something.

FWIW, to anyone reading, this is our current workaround. It's not perfect at all, but it can help:

1) create a custom issuetype called "Sub Task", obviously not a true subtask but it can work. Assign field that you think make sense.

2) create a story as you would normally

3) Create issues of this new type, sub task, and set them as blocking the story story. This can at least help teams understand what "sub tasks" are required for a story to hit definition of done without true subtasks

May not be ideal but it's worked for us so far

Hi Eoin,

Thank you so much for chiming in. It is fantastic to hear something from Atlassian.

It becomes really difficult when there is no information at all.

We were using Angular 2 when it was still in Alpha. It was tough going at times, but the Angular 2 team kept us up to date with what was happening. We could also see that there had been updates because there was a new version number.

We are software developers too and we know it's not always possible to do what the Google team did. But it would be great if there was some way of knowing that updates had happened. Perhaps you could include the version number in the page footer. So even if it was just a performance issue that was fixed, we could see something was happening.

Regardless, I am also very excited about next-gen. It's obvious you've given yourself a huge task but we know from your record it will become a reliable, robust and mature product as soon as possible. I congratulate you for taking it on. So please be encouraged and I look forward to whatever improvements you are able to incorporate.

Thanks

Chris

Hi again, Atlassian,

I really love working with you guys, and your support rocks. Jira is a great product, and I'm really excited to see its future. However, for many of us in the agile world, this is a critical feature in keeping our tasks organized. It's completely understandable that doing something right, especially when it needs to fit in to a new flow and such, takes time. The only thing I think some of us would appreciate is more transparency on where this critical requirement is at. You guys know as well as we do how important this sort of organization and relation is to agile development and keeping our goals aligned with the business needs.

Keep up the great work all, just please maybe some more bits of info.

Thanks!

Hi development team,

My company (200+ people) decided to choose Jira Cloud as our tool of choice for project/task management, and Next-Gen projects is a promise that has heavily influenced the decision to choose Jira Cloud. But, now I'm getting concerns about this since there were no significant visual and functional improvements on the next-gen projects in last months, with sub-task being first on our list.

Can we please have someone (a PO or a product manager) ensuring that this is getting into the product soon, and what does soon mean?

Thank you

+1 

This is blocker for me in terms of moving over to next-gen projects.

We really need a date for this, as it was released to Cloud users without notice, teams have been setting up their own projects and then our own internal Jira Admin team have had to recreate the projects in the older versions as this simple feature is missing. I need to provide a date for the higher ups as with all the functionality changes and things missing it is getting harder to justify the rising costs of this product.

+1 

Is there an estimated date?

I find the workaround above really annoying.

Atlassian came out with Next-Gen with a big blast and gave the impression everyone switch to next-gen for their next project.

But now we find this project is really still in Beta (or probably even Alpha) with important features not yet even implemented.

This issue is not even assigned yet.

But the workaround virtually says "play around with next-gen and let us know what you think. But if you want to track a real project you'll need to use Classic.

Can Atlassian at least put large warnings on Next-Gen telling us this is still in Beta and not ready for serious project tracking.

Particularly as this issue was raised on October 1 last year and it appears no work has been done on it yet.

At the moment I would have to say I am VERY DISAPPOINTED with next-gen. I was willing to forego sub-tasks for a short time but how long are we going to have to wait?

Is there a date set for this release?

Eagerly awaiting this feature! Currently we just make stories, and have a custom type called "subtask. Those get related as blockers to the story. It's not ideal, but for the purposes of organization it works

+1

@danieltaylor https://www.atlassian.com/roadmap/jira-software#results is the roadmap for what's coming

+1

+1

Anyone know if there is a place we can go to see the plan for when (and whether) this feature is coming?

So your workaround is: Don't use our new feature, it's not for you... Yeah right.

https://www.atlassian.com/roadmap/jira-software#result-dc7a9a9c says that Subtasks are coming soon.

In light of your "Workaround", is this now not the case?

+1

This is a must have, or else there is no point keep using Jira (which already is way too complex for no good reason)

+1

+1 I would love some sub-task action!

I also can't use "next-gen" projects without sub-tasks

Any idea when sub tasks will be added to the Next-gen projects?

Subtasks are shown as part of the Atlassian youtube video for announcing "next-gen" projects so it was surprising not to see the feature when i tried it for the first time today.     

I just ran into the same thing.

I also didn't intend on creating a special 'next-gen' project when I sought to create a private project - but it seems this is what happened.  Now I'm finding standard functionality missing like the ability to create sub-tasks.

A team set up a next gen project by accident when wanting a simple Kanban project. The first question that was asked was what had happened to the Sub-Tasks. This is currently a deal breaker for switching over to the next-gen project style, which is frustrating as the Roadmap View, simplicity or set up and use, as well as the project not sharing configurations with others on the instance is desperately needed by the teams I work with.