Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2018 edited
Glad to hear you like the simplicity of next-gen projects @Craig Grant. Thanks for the feedback on logging work. This is something we plan to add in the future but it isn't something the team is actively working on right now and so we haven't added it to the public roadmap yet.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 29, 2018 edited
@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
Yes HIPAA is definitely on our radar – we don't have a timeline we can share right now but we are actively assessing the steps we need to take to offer this.
Hi! It’s a really wonderful change. I want to transform my others software projects to this type of projects. I have Jira Cloud. How can I do this? Can you healp me?
Echoing other comments here, this looks really great in terms of usability features. However, across an organization where we have a lot of process, reporting, and automation built around shared workflows, statuses and custom fields it's just not viable to have projects exist in isolation.
Some questions, if I may:
Regarding workflows: you mention eventually sharing templates with other next-gen projects. This would only be useful for us if a template is a single source of truth, which can be updated once and reflect in all projects using the template. Is this the plan?
We would be very happy if the excellent next-gen field management screen was made available for classic projects. Primary/secondary field ordering is sorely lacking in the new UI for classic projects, it'll be pretty unfortunate if new features rolled out across Jira are only manageable in next-gen projects. Is there a plan to provide this for classic projects?
Advanced workflows and templates don't appear in the public next-gen roadmap - do you plan to add items which are further from implementation, like these?
Additionally, any comment on future development between the next-gen Roadmap and Portfolio (if any) would be welcome, thank you!
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.
I’d recommend trying out a next-gen project with your team to make sure they are comfortable before you move issues over from your Classic project using the bulk move operation.
This bulk operation allows you to move multiple issues at the same time. The issues you're moving need to be mapped to both a project and an issue type, and in doing this, you may need to also map the status and fields of the issues. Subtasks need to be mapped, too.
Perform a search with the required filters to produce a list of issues.
Click more(•••)> Bulk Change all<n>issues.
Select the issues you'd like to perform the bulk operation on, and click Next.
Select Move Issues, and click Next.
Enter the requested information for the issues you're moving.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 30, 2018 edited
@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 want to implement some level of consistency / standardisation across projects, where some of the configuration will need to be centralised, not delegated. Our aim is to give you the choice that mirrors the choices you make at your organization regarding how much autonomy vs control you give teams.
2. No. There are no plans to take next-gen's configuration UI and apply them to Classic. There are some significant architectural changes under the hood with next-gen, particularly how configuration is no longer dependent on schemes and the associated complications with how they might be shared. Also there are new features like Roadmaps that do not work on Classic. The differences run much deeper than just a new UI.
3. The public roadmap will be updated as items are getting closer to implementation and so what you see there are items that either already in dev, or just about to enter dev. Advanced workflows and templates are a little further away than what we've currently published on there, but we're very keen to share news at the earliest opportunity and so we'll be sure to update it as we get closer.
Roadmaps is still very new and we have some work to make it integrate really well with the rest of the project. What kind of things would you like to see with, say Portfolio? Is it the cross project views or higher level rollup that you need?
Atlassian Team members are employees working across the company in a wide variety of roles.
October 30, 2018 edited
@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 process control you might need.
Again, it would be very kind if you could include the roadmap feature into the last generation projects as well. So that we don´t have to move with projects
Atlassian Team members are employees working across the company in a wide variety of roles.
October 30, 2018 edited
@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 projects, you cannot drag and drop between the (swimlane) groups.
In next-gen you can drag and drop between groups, to say, change assignee and epic simply by dragging the cards between the rows. This is something we want to preserve as best we can as we add more customizations in for the group by feature.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 31, 2018 edited
@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 to Ability to star your favorite projects, boards, issues, filters, and dashboards as we're still working on a post for that one. Will update when that is ready.
Atlassian Team members are employees working across the company in a wide variety of roles.
November 1, 2018 edited
@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.
@Jason Wong I realize this is old, but I just found it while searching for a way to star issues. One of your bullet points states "Ability to star your favorite projects, boards, issues, filters, and dashboards." Where exactly is the UI for starring an issue? I see the option on projects, boards, etc. but cannot for the life of me see anything on an issue (using the "new view") that would let me mark it as a favorite (in cloud).
Atlassian Team members are employees working across the company in a wide variety of roles.
January 14, 2019 edited
Hi @Denny Raphael - can't say at the moment. Our Jira Server team is closely watching the feedback on Cloud to guide what features they will deploy next. Server is currently balancing more on performance, administrative control, and team productivity in Jira. For more, please check out the Jira Server keynote at the most recent Summit in Barcelona here.
Atlassian Team members are employees working across the company in a wide variety of roles.
January 14, 2019 edited
@Esther Strom - good spotting. You can indeed star projects, boards, filters and dashboards directly on the page, except for issues which can only be starred from the navigation drawer. We're working on bringing this more into the issue so make it more accessible.
Where can I find a succinct table of Classic Functions lined up with Next-Gen Functions, and which are compatible with each other. An example would be "Epics: Can I assign next gen issues to classic epics, and vice versa?", or "Time Tracking: Can I get a consolidated report of Bob Smith's Time for both Classic and Next Gen issues on one single report?". I'd like to permit both Classic and Next Gen projects; however, manually reconciling stats for the two are a scary thing to face. With a list of shared and unshared features, at least I can do an "informed consent" for new project teams.
126 comments