What I don't get is why not bring these features (project specific custom fields, roadmap) to already existing projects. Why have to make a completely different project type for this
Next-gen projects do nothing for me. Having boards under a single project is a nightmare but so is most of the new navigation.
The new issue view is a nice idea but it's still missing features. The dumbed down text editor is especially annoying. Please bring back markdown for experienced users.
The new board may be shiny but hiding the quick filters in a dropdown must be this year's worst decision. When are you rolling back that disaster?
You have made 1 useful change in recent months: a dropdown list of projects to copy the settings from when you create a new project.
I still can't hide time from certain users (is that the most-requested yet longest ignored feature for Jira? This important feature has been requested by serious users for 15 years! Yes.FIFTEEN YEARS!
I also still can't see which project permissions are given to a user group (I can see the same for users, so why can't you do that for groups?)
Seriously Atlassian, I'm getting really frustrated with you guys.Can you at least get some of yourdevelopers away from fiddling with shiny UI's and develop some useful features?
Hopefully this does not force users to the new issue view format that is currently being tested in the the cloud implementations. It's not user friendly. I'm getting very tired of clicking "See the old view" over and over again. I'm hoping there is the ability to keep the old view and tab structure we currently have. I fail to understand why Atlassian doesn't listen to their consumers. I have to go to the old view. The new view is not intuitive. Where is the edit button? How do I get to my existing tabs (absolutely required for me to work). This new view is causing me pain and I am not even forced to use it yet. I will vehemently oppose any upgrade to this version. I am not too optimistic that you aren't going to force cloud users to the new UI like you did with the last horrible upgrades. It has been quite a while since I started using the new format. I still dislike it. Unlikely we will go through the work to change at my present company but eventually I'll have input if I go somewhere else. Jira will likely be off the table if you force us to upgrade. This is not Chrome. Chrome forces upgrades that occasionally break things but we aren't paying for it. Forcing any type of upgrade in a critical system is not going to make me a fan.
@Henrik Öquist I actually just found out how you can currently do #2 in your list. If you hover over the card on the kanban board, or the issue in the backlog if you have that enabled, an ellipsis will appear over the card/issue. Click that and there is an option for "Add to Epic" or "Change Epic". My intuitive approach was to open the epic from the road map and attempt to add the existing issues there. It'd be a good idea to allow users to create/add existing child issue to an epic instead of just create.
Something interesting that I found while poking around trying to do this. It seems that the epics created in a Jira 2.0 project are not the same as previous epics. I attempted to use the search/bulk tool initially to add the issues to the Jira 2.0 epic and Jira threw an error saying that the Jira 2.0 epic is not the correct issue type for epic.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 24, 2018 edited
@Block, Greg Hey, I would like to help resolve your issue but need a bit more information.
Can you send me a direct email: tpechacek (at) atlassian (dot) com
Or just follow up with a reply here:
Can you provide any screenshots of what you are seeing?
We are trying to reproduce, seems like this is a Zephyr issue given the TypeError and is happening on the iFrame side of things. Have you tried raising a Zephyr support issue on this?
With Chrome, has the manual refresh always been the case, or something you noticed recently.
Thanks in advance, hopefully we can resolve this with you quickly.
When do we get this stuff for Jira Server? It's confusing to announce new these Jira features when it's not clear to the untrained eye whether these are for cloud or server. Still tons of server users out here. :)
It would be great if there was a link for each of the 10 items above that went to documentation on how to implement the new features or specifically how they work.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Moving on from my first comment....I really like the new experience. I wish epics showed a wee pic of the person assigned and maybe even allow us to change colours. This will work great for reporting to the business on what our roadmap looks like :)
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2018 edited
@aponski, @Kevin Lau & @Rafael FrancoThe 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 project experience.
An example of the differences vs Classic are that Next-gen epics: a. Exist only at the project level, not across the site / other projects. b. You can now rename epic to whatever you like eg. Feature
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2018 edited
@Furqan Iqbal Hi! I work with Jason on the Jira Software Cloud team.
Subtasks aren’t available yet, but they are on the way! If you take a look at our public roadmap for next-gen projects (https://www.atlassian.com/roadmap/jira-software), you’ll see that subtasks are at the top of the list and will be coming soon! Thanks for trying out the next-gen projects, I hope that you’re liking them (even without subtasks)!
Jake here, and I work with Jason on the Jira team. Rest assured we have no plans to leave our Server products behind!
Jira's Server offerings remain a core part of the business and, as you might have seen at our recent Summit in Barcelona, we're making enormous investments in both Jira Server and Jira Data Center as well. Our end goal is to give customers the flexibility of deployment choice and if you're a Jira Server user you continue to be in very good hands. You can watch the Jira Server keynote at Summit Barcelona here.
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2018 edited
Hi @Dom Baldin [Adobe] This is Corinne on the Jira team. We’re so thrilled to hear you and your customers are digging the new Jira Software Cloud.
Our Jira Server team is closely watching the feedback on Cloud to guide what features they will deploy next. We can’t promise when (or if) specific features will be deployed in Jira Server, but we’ll be balancing which elements of the Cloud experience would be most valuable with our other priorities around performance, administrative control, and team productivity in Jira.
Hope this helps!
PS - We're excited about the new Jira Cloud XD integration!
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2018 edited
@Jason Freeman Hi, I work on the Jira Software Cloud team with Jason.
I’m sorry that the post wasn’t as clear as it could have been, but next-gen projects and these changes are only part of Jira Software Cloud and aren’t included as part of Jira Service Desk. The next-gen Scrum and Kanban projects have been designed for different workflows and won’t impact your team’s use of JSD.
My name is Jake and I work alongside Jason on the Jira team.
Jira's Server offerings remain a core part of the business and, as you might have seen at our recent Summit in Barcelona, we're making enormous investments in both Jira Server and Jira Data Center as well. Our end goal is to give customers the flexibility of deployment choice and if you're a Jira Server user you continue to be in very good hands. You can watch the Jira Server keynote at Summit Barcelona here.
My name is Jake and I work with Jason on the Jira team. Thanks for your question about migration!
The current Jira Software Cloud next-gen experience will live alongside the classic experience. We have absolutely no plans to force anyone into either experience and are actually seeing most teams creating both project types. Please continue using your classic projects for as long as you'd like!
126 comments