Eoin Atlassian Team

@Laurin Stoll we'll continue to build out the next-gen projects to have the same power as the classic projects - but we have no plans to force users off classic projects. We'll be hoping to make the next-gen projects so good that you'll want to move over!

@Vicki Lea Tsang we will continue to build out the next-gen projects to have the same power of the classic projects. The role of the admin will not be something that can be replaced so please don't worry. It will hopefully mean, however, that you have more time to do the important tasks and it's easier for you to manage…

Thanks @Kerekes Melinda. It's worth playing around with the new project in the meantime anyway. Feel free to drop us feedback on the things you would like to see the most

@Romain Vinet @Manu Lohiya @Ken Casier it's a possibility but it's not currently planned. We are full steam ahead to build out all the power that it's in classic projects into the new next-gen projects. @Ken Casier there is no one click migration but you can move issues to a new project using the instructions here

@Alejandro_Gómez_Montoya we've taken on sub-tasks and workflows as the next big items. Time tracking is likely next on our list after that. I hope this helps as an update.

Hi @Tomasz Szadziul - it's possible to add a rule to set an assignee upon transition an issue to a new status. Manage Rules is available in the top right meatball on the board view. Let me know if this is what you were looking for.

@Abhijith Jayakumar we don't have the ability to do this in an automated way right now. We will look to rectify this. Thanks for your feedback

Hi @Manu Lohiya. We have created a new work hierarchy in Jira to allow us to create more structure going forward. Providing backwards compatibility for the Epic Link in the classic projects is something we're currently investigating. And we've yet to introduce a JQL function for the new parent/child hierarchy. Apologies…

Thanks for the question @Darren Lyons. We will be building out kanban specific reports/metrics in the future, although we've got a few big features to get through before we'll get to these (work breakdown, workflow configuration)

We're starting to work on sub-tasks next week. I can't give you an exact timeline I'm afraid but I am hoping to have something available before the end of the year.

@John estimate roll ups is definitely on our list of things to do :) We've got a few other big features to get through first but it's coming!! Cheers

@Craig Grant we're focusing on work breakdown and workflow as the next two major items on the backlog. Time estimation and tracking are most likely next up after those. Cheers

Thanks @Artur Wisniewski! This feedback is great - really helps mus understand your needs and with our prioritisation. Cheers

@gestj paralell sprints will be something we build in although we've got a few other big rocks to get through before we get to this! Thanks for the feedback. 

@Nelson Ra you got it! We'll continue to build out the power. Workflows are up after we tackle sub-tasks so hopefully you won't have to wait too long. Cheers

@Nataliya Pennie the ability to customise card layout will be something we come to - and due date is up there as one of the first fields that would become available with this. Changing card colors is something however we're still considering - keen to hear how you use card color? It would help with our prioritisation.…

tomi.hokkanen@kone.com we'll definitely support multiple boards in next-gen in the future. We've got a fair amount of work on before we get to that - including improving work breakdown, workflows, estimation, and managing completed work. Exciting times! Cheers

Thanks @FabioCalo for continuing to give us feedback. As Mark and Paul alluded to this is indeed by design. We try to find the right balance with being opinionated and where to allow you work whatever way you want and this is an interesting case. It's something we'll revisit so you're feedback is helpful - an alternative…

@Daniel Pérez it's not possible to do this. You will need to create a new next-gen project. Feel free to leave here what you think are the main barriers to you adopting the new projects and it will help us prioritise our upcoming work as we build out the power on these projects. 

@Derek Daigrepont the new next-gen projects are different to the classic projects. We will begin to treat Scrum as a template from which your team can start and then adapt over time. Similarly Business will be a group of templates - e.g. Content Management would again be a starting template from where your team can adapt…

@Ian Sheffield thanks for all the questions. I'll try answer them one by one. Rolled up estimations is not in the first iteration of estimation. However, this is absolutely something we will look to solve - and I'm sure will be a spicy one :) We are building the concept of work hierarchy into Jira Software next-gen…

@Hasani we will build reports over time. More importantly we will look to surface key information in context as well as providing a place to create and share reports. It will help us alot if you could tell us what reports you use and what you find them useful about them?

@Wouter Eijkelenkamp story point estimations are fully rolled out as of 2 days ago. Is this what you are looking for?

We've just a public roadmap to help give you all a way to see what's coming soon with next-gen projects... https://www.atlassian.com/roadmap/jira-software

@Robert Fink Resolution is something we're going to look at when we get to workflow configuration. This will be after the next iteration of work breakdown.

@Damian Skrodzki we're considering this as part of an innovation sprint next week. Do you want to email me at eryan@atlassian.com - may be an opporunity for us to partner on it? :)

@jo we haven't built versioning into next-gen projects yet, although it will be something we work on in the future. Love the idea of using labels for versions in the meantime. Keen to hear how this works out for you and whether there are some quick wins on how we could improve this.

@Robert Fink not yet but it's next on our backlog! Just finishing up with story point estiamtion at the moment.

@Levon Mkrtchyan we'll work on sub-tasks next and checklists (actions) will also be something that will come in the future. I'm curious as to whether you see a need for both of these or whether something like checklists would give you everything you need?

@Joshua Sabol with estimation turned off (we're currently rolling story points out) the reports work on issue count.