Jason Wong Atlassian Team

Hi @[deleted], We haven't built a great way to move from classic to next-gen projects. We're currently prioritising the build of more capabilities into next-gen, which will increase the demand for people wanting to move. We understand that many teams are super busy and so in the future we will work on a better way to…

Hi @Abel Lineberger, Right now, Portfolio isn't fully compatible with the new project experience, primarily because we have re-imagined issue hierarchy in next-gen and are working with a new data model. The new experience will continue to be built out from a hierarchy perspective, so that we can support levels like…

Hi @Werner Anders, The new Jira issue view is still being built to handle more and more complex functionality. * The share button is on our roadmap and will come back sometime in Q3 FY19. * Drag and drop file attachments should be working - you should be able to do this by dropping it anywhere on the issue (which would…

Hi @Jayme Rabenberg, Firstly thanks for the huge interest in moving to Next-gen. We have a lot of requests for more help moving from classic to next-gen. We are adding some highly requested features, such as sub-tasks, more field configuration, and refinements to epics (which you can track on our public roadmap) and in the…

Hi @Justin W. Arndt, Having rich information available at a glance is definitely something we want to provide on the cards, and ideally we would like to go one further by making it specific to your team. Like with the issue view, the card view has its own system that determines where specific content can be displayed and…

Hi @Warren, This is a great question and I'm happy to share some insight into this! The 'new issue view' has been built to be native for next-gen projects and so for those project types it cannot be disabled. For next-gen projects, you can already customise the layout of the right hand side of the new issue view. To do…

@Jamie Aquila the new next-gen projects do not yet have a dedicated place to manage releases and have yet to enable versions. We will be doing that in the future, so please check our public roadmap for updates.

@Dave Furlani thanks for requesting more info on each of those features. I've come back with a bunch of links. Just adding bold below for the benefit of others who have also expressed interest in more info / images. UPDATE: the blog post now has a link in each of the features, except for the one about the ability…

Hi @Corey Thokle You can rename your board by simply clicking on it's title inline at the top of the board. Something like this

@Francesco Racanati we will provide more customizations to the group by functions. We will start by introducing a more simplified way to specify a custom views with a more use friendly interface - similar to say basic mode in issues search, which builds a filter for you in the background. You'll notice that in Classic…

@james greenwood you could map out an approval process in next-gen, however I would caveat that it's more optimised for agile software development teams with minimal formal process. If you have a strict approval process, you will most likely need to wait until we implement more rules and workflows in next-gen to get the…

@Iain McCarthy I'm glad you're sounding out the need for custom templates that are and consumed by multiple projects. 1. Yes. What you've described is the general direction we'll be taking for templating in next-gen projects. In addition to the new fully independent projects we've released, we're anticipating that you'll…

Hi @Ala Martinez, Pleased that you like the changes. To move over, try setting up a next-gen project the way you want to project to work with the columns, issue types and mode you want to run it in eg. With or without sprints, with or without estimation etc. Here’s an article to get you going…

@[deleted] - over here https://community.atlassian.com/t5/Jira-articles/My-Top-10-Favorite-Features-in-the-New-Jira-Software-Cloud/ba-p/918727/page/3#M689 @Jake beat me to the punch ;) I will however add that Classic and next-gen project differences run much deeper than just UI changes - as you mentioned, there's…

@גלעד כץ glad you like the new roadmaps. Moving over is still a manual process but it is possible. Please see this comment from @Julien Femia on an article about getting started on next-gen for the steps. Thanks to so many people on this article asking for an easier way to move from Classic to next-gen, I think it's…

@Recruitment Bot glad you really like the new experience. See a few of my comments above - moving over is still a manual process but it is possible. We're thinking about how to make the move easier for you. We'll take your requests onboard as we continue to improve the new epics. You'll be pleased to hear that we will be…

Hi @megha kuruvilla to move from an exiting project to next gen is still a manual process, but it is possible. Please see this comment from @Julien Femia on an article about getting started on next-gen for the steps. Please let me know how you go.

@Jerônimo Lopes thanks for telling us your needs and what you'd like to see in the new next-gen projects. I think what you'll find is that we'll be building more capabilities into the next-gen projects, which will then raise the demand for help with migrating over and we'll need to figure out how to make the ove easier…

@Dave Furlani a few people on this thread have also requested more info about each of those items so we'll come back with some links to the various pages that go into more depth and provide visuals. From just reading them, which ones stand out?

@Alan Williams glad you asked about how this will help with scaling. Please see my comments above to Brian and Lynn regarding our future plans to introduce templating for next-gen projects to help you achieve things like consistency of fields across projects. 

@Brian Strickler, @Lynn Stahl apologies for the delay in getting back to you. It's been a huge week for us here with the announcement. I'm glad you love the workflow configuration in Classic projects. Jira will never lose its workflow configuration power. More powerful workflow configuration, will eventually find it's way…

@David Ducrest sorry to hear your experience over the past year. Can you tell me a bit more / give examples of where the improvements over the last year have been slowing down your productivity? Many of the features I put on the blog are only available on Jira Software Cloud's next-gen projects. You can continue to use…

@Benjamin Peikes yes, we've still got some way to go with adding more advanced and powerful features to next-gen projects. There's a public roadmap here for visibility of what's coming next, but I wanted to let you know that more powerful workflow configuration, such as what you have with Classic projects, will eventually…

Hi @Sarah Pinns glad you're liking these new features! I just wanted to get back to you that these features are only for Jira Software Cloud. Apologies for the confusion with the previous title of the blog post - we've updated it to make it clear that it's for Jira Software Cloud. As to when or if the features are coming…

@Samuel Engelman there is indeed a lot more to come - for visibility please check out our roadmap https://www.atlassian.com/roadmap/jira-software for example, drop down custom field and story point estimation was added this week.

@Casey Graves & @Henrik Öquist - epics are indeed different in next-gen projects and not the same as previous epics. They are scoped to the project, meaning they don't run across projects and the parent to child relationship is a lot stronger than with the previous versions. The benefits of this will come through as we get…

@aponski, @Kevin Lau & @Rafael Franco The next-gen projects are built quite differently to Classic so while Roadmaps works with next-gen, it actually doesn’t work with Classic. It’s not that we’ve hidden the feature or anything, it’s just that they are built differently and so we have decided to optimize for the new…

@Hari Suminto I’d recommend trying it out with your team first before deciding if you are ready for the move. You can then bulk move your issues from any other existing project - see comment here on how to do that - https://community.atlassian.com/t5/Next-gen-articles/Getting-started-with-next-gen-projects/ba-p/914448#M233

@Kevin Tran We have yet to add back in resolutions for done issues. Right now we’ve compressed that into the last column to make it simple but we’ll be working to bring that back. Sub-tasks are not there yet, but they are coming soon. https://www.atlassian.com/roadmap/jira-software

@Shengyu Chen Great to hear you're liking it. What you describe seems strange. There are 2 ways to add people to your project. * On the top of the board and * Project settings -> People. Are you still getting empty results when you type the person’s name or their email address? If so, I think we need to look into your…