Basically you have released a beta version of the software. I was forced with out any indication that my new project was a 'new-gen'. Added an epic - very buggy - pop up box kept losing focus. When done - my epic disappears - I see the heading in places, but can not see it, add to it, assign it or add sub tasks.
Cant add a Kanban board and cant create an old style project - so you are forcing to use a useless bit of software on me. What is going on????? I put in a support request and I hear nothing.
This must go down as a complete ham fisted release. If I did that with my clients they would find another vendor ASAP.
This is awful. Absolutely useless. How can I disable this for all my users?
Seriously, I do not want people creating these projects. I was quite happy with having only selected admins being able to create projects. Especially since you CAN NOT MIGRATE to a normal project.
What would be useful is if someone can start setting up a project and afterwards you can migrate it to a proper project with all the settings I need but you can't. Your so-called migration means create a new project from scratch and move the tickets across.
Atlassian never stops disappointing me.
This is the best development in Jira in the past few years:
This is what is really taking the pain out of setting up a project.
The ability for all users to create projects, brings me as an Admin to constant monitoring of what was created when. As then questions arise, and I first need to check. Maybe a notification of project creation for company-wide admin would be nice.
For anyone else who doesn't like their whole company creating projects:
Go to Jira settings > System > Global permissions.
At the bottom of the page you'll find "Create next-gen projects" which by default is given to "Anyone". Remove "Anyone" and give the permission to the people you want to create next-gen projects (in my case: nobody).
Atlassian Team members are employees working across the company in a wide variety of roles.
October 14, 2018 edited
@Michael Brown your project admin currently controls the swimlanes on the project as its currently impacts how all users view the board. It is shown as "group by" on the board. We'll look to make this a user specific setting in the future!
Atlassian Team members are employees working across the company in a wide variety of roles.
October 14, 2018 edited
@Ben Watson next-gen projects are new within Jira Software and there continues to be the classic projects that you are familiar with. It's most likely you do not have the permissions to create a classic project if you do not see that option, but your admin can do this for you.
We're working on making it more clear on project create what is and isn't available within the next-gen projects to try avoid the situation you found yourself in.
As for the epics - they are are managed in the Roadmap view in next-gen projects . You can also assign issues to epics from the board and backlog views.
Hi again, I have some insights and questions regarding the use of sprints in the new project.
I really like the feature of been able to create a task, or issue in general, directly in the board by clicking a "plus" sign under the user, but it seems that this is not available when using sprints and consequently any new issue goes straight to the backlog.
Another feature that seems to disappear when using sprints is the ability to Click on the "Looking for older issues" link at the bottom of the Done column where I could see done issues moved to the repository.
Also, at the moment I have a general sprint (in order to generate reports) with general tasks that appears in the board, but when I create a second sprint with more specific tasks for a selected group of users the sprint or tasks associated with it does not appear in the board or the users assigned to them. How could I be able to have several sprints in the board for users to see?
I really like the feature of been able to create a task, or issue in general, directly in the board by clicking a "plus" sign under the user, but it seems that this is not available when using sprints and consequently any new issue goes straight to the backlog.
Isn't that by design? Traditionally, when working in Agile new issues should go to the backlog and not into the current sprint because the scope has already been set.
It is by design -- but everyone has different use cases. In our case the lighter "Trello-like" construct works for us. Being able to quickly add items to the board and yet still have the backlog works better for us. Sprints are more fluid than traditional "Agile methodology" in our work.
Is the Agility project type is the first of several next-gen project types? That seems like the direction. If that is the case, is the plan to create next-gen projects for each of the current project types (Scrum, Business, etc.)? Or, will the next-gen projects be conceptually different than the older project types?
I would really like to start using the Roadmap feature of the Agility project type, but the lack of advanded features is too limiting for me to convert just yet. So, I am wondering when those other next-gen project types will be available.
I know that these changes are prefaced on user feedback and wild numbers are thrown around to justify it. I also know that with change comes difficulty and you will get noise from people who don't like change.
So I give this feedback in the context of me being an early adopter and in most circumstances I find the benefits in change. I feel you are making changes for the right reasons, but the changes themselves are horrible and do not actually satisfy the issue faced in the feedback that justified attempting them.
These next gen projects lack the functionality to actually be useful. I can see they might get to a good place one day, but they are not there yet.
And having to deal with that disappointment is compounded by the absolute mess that is the new issues view, which is hands down one of the worst changes I have ever seem in a piece of software.
I know that these two major mistakes made by atlassian will ensure I do every thing I can to more away from this software in any organisation I work for.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 18, 2018 edited
@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 over time.
The main difference with today is that the projects are quite inflexible - they are really project types - and it's more diffuclt to adapt the poject to the way your teams changes how they work over time.
The new next-gen project type, where we have made two templates available right now - Scrum and Kanban, will grow in power over time as we build it out. As we do this more and more templates will also become available for this project type over time.
We have no plans right now to build the Roadmap feature onto the classic project types.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 18, 2018 edited
@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.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 18, 2018 edited
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 for example is to allow create in the first column and present you with the scope change warning - we'll continue gathering more feedback and iterate if it's cause more issues than solving.
The Looking for additional work link is an interim step for users of Kanban to find work that is automatically cleared from the last (Done) column. For Scrum the sprint must be completed for work to be cleared off the board. This will be an area will tackle with another iteration when we get through the next iteration of work breakdown (where we are going to introduce sub-tasks). In the meantime, the easiest way for you to find completed work is to the use the global issue search... https://confluence.atlassian.com/jirasoftwarecloud/searching-for-issues-764478280.html#Searchingforissues-SearchallofJira Apologies for the inconvenience here.
Parallel sprints is also something we have not got to yet and the board only shows work from the active sprint. Again this will be something we do in the future.
I hope this helps. Let me know if you need any additional information.
The new, next-gen roadmap feature looks nice, however we find this "Gantt type" display for roadmaps or planning of little use.
Epics are thought of as "larger chunks of work". But the roadmap UI only allows an epic bar to appear once in the time line. So, if you want to use your epics for roadmap planning, you will end up with very long epic periods, depicting lead times that may not have any relation to the amount of work that is to be done in that epic.
As an example: suppose an epic is about building a part of a UI. The epic holds 2 stories. Both stories a about 1 day of work each. What if the time between doing story 1 and 2, is 3 months? The roadmap will show this epic as a bar stretching 3 months, whereas the amount of work is only 2 days.
A better solution would be to allow multiple bars of one epic to appear in the same row. That way, you could show that the epic will be worked on in different/several points in time.
And as a feature request: add people to this and resource planning is born.....
The new next gen project looks interesting but unless there is an easy way to port a classic project to a new one, we will have a hard time moving over and fully exploring the possibilities in our project
This is an intriguing and fresh approach and I honestly believe the migration will pay off for us in the long range.
The roadmapping capability is wonderful and starting to move in the Porfolio for Jira direction, to fill a needed gap in managing the Agile process. Nice job.
BUT, as far as I can determine, the migration path itself is not viable at this point. My thought was to build my epic-based roadmap "fresh" in the next-gen project and then to move existing issues into the specific epic they will be assigned to from our classic project. However, there are 2 roadblocks:
- if I try to do the move directly from the classic project, the error "<epic-id> must be an Epic type" appears if I try to assign the issue to the epic I've built in next-gen
- if I move the issue to the next-gen project and then try to associate it with an epic, there is no mechanism i have found to do that association. All I can do is make it a "linked issue" (but can't make it a child of the epic).
Am I missing where to make that association or is it just not there yet?
And if it's not there yet, do you know how soon it will be?
Thanks for the great work. It's not easy rebuilding something from the base up, but it will be worth it!
402 comments