Any chance we get a better integration with bitbucket? Now this is just a hacked on, totally separate (paying) product which happens to have the same username/password.
No better integration than let's say using Github.
It's awesome to see you guys approaching these design challenges. They're big for sure, but I think you're tackling some of the biggest pain points in JIRA head on. Good luck!
The problem I face with this is that it takes up more vertical space - when you're using a wide aspect monitor (e.g. laptop display) vertical height is at a premium. When we look at the active sprint details, for example, there's hardly any room for the issue cards (can only see a couple of rows already, even with the old navigation arrangement).
Can we get the same new navigation as a side-bar please?
For Phil’s concern, it would be nice to be able to collapse the top horizontal nav when needed (a way to hide it and a small hamburger menu icon remains in the white space... gives us more use of the real estate when needed).
However, to echo many others, you should bury "Your Work" and "People" (especially while People is still being built out). Anyone that actually knows how to use Jira will prefer a dashboard over "Your Work" .... they will set it up to be customized exactly the way that they want. Sorry, my post was not originally going through due to formatting and now it split.
Make the top bar only have Projects, Filters, Dashboards, Create and the Search Box. Regular users never need to go to Apps or People. Admins should just be clicking the . on their keyboard as a shortcut to get to all of the important places that they need to be to administer things like apps. When you click the logo, you get to "Your Work" anyway... just get rid of that using real estate. Now you will have a super clean UI. If you really want to bring back People later, you can... but no one needs to use that ever (they can just hover on a profile card and click into "View Profile" if they care about that information... it is always driven by a Jira issue first... no one is just hanging out in "People")... and if they really want to peruse it, they can click it at the bottom of the search section (the place that you have relegated Boards). On a positive note, @Matt Tse thank you very very much for actually engaging with us over this change. We are all really appreciate of your responsiveness and I hope that you get rewarded, that your colleagues strive to emulate you, and we can make Jira/Confluence Cloud better every day (ship faster, listen to the users with these feedback loops, and change course... be truly agile). Sorry about the long post everyone.
If you’re signed up for our Early Access Program (EAP), please disable the Atlassian Chrome extension as it might be conflicting with the official build. Please note that the Chrome extension was built purely as a proof of concept for us to test and share the designs early with customers. We will not be improving the extension, so if there are bugs that prevent you from doing your work, we would recommend turning it off and sticking with the current navigation for the time being.
Thanks for being part of our EAP. We’re so glad to hear the improvements are resonating with you. We can’t wait to get this out to more customers as well!
We're building up interest in bringing a dark mode to Jira. If you haven't already, please check out our public Jira issue and follow it for the latest progress: https://jira.atlassian.com/browse/JRACLOUD-63150.
We think so too! If you have any feedback you’d like to share about the old experience, we’d be more than happy to hear it. Feel free to email me at mtse[at]atlassian[dot]com.
These changes will not impact the current issue view experience; however, the Create button will be a lot more obvious and accessible from the top. Depending on how your Jira instance has been setup, you should be able to use the (c) shortcut to Create an issue and create a link directly.
These changes will impact both Classic and Next-gen projects. They will also be in effect for all our Jira Cloud products: Jira Software, Jira Service Desk, and Jira Core.
While we’re also excited about the improvements these changes are bringing, we know how equally (if not more) important it is that our customers and users feel in control of the changes. This is why we’re starting with the experience off by default so that we can minimise the disruption caused and allow users the time to learn and switch over when it’s most convenient.
Not to worry, the issue view/edit/create experience will not be impacted by these changes we’re making to the navigation UI. If you do have feedback about the issue view experience, please visit JRACLOUD-70555 - New Issue View in Jira Cloud
One of our key values at Atlassian is to do right for our customers. In this instance, we received overwhelming feedback from customers that the current navigation in Jira Cloud was limiting. To do right for you we designed a new navigation that over 95% of early testers preferred over the current one. We understand that change can be tiresome. To minimize the impact of this change we want to put you in the driver seat and give you flexibility when you roll out the change. If you want the new navigation early, you can sign up for our early access program or opt-out until a later date. We also are letting you know now (many months beforehand) so you can plan accordingly and minimize any disruptions.
Who doesn’t love the holidays?! We’re so happy to hear that you’re excited. We are too. Once the new navigation is made available to your site, please let us know how you go!
Yes! Apps will function exactly the same as they do today. We will be making them more accessible and easier to access by having them grouped into the global navigation menu. Having it here makes it easier to access the Apps from anywhere in Jira.
You got that right. It’s not exactly the same as the server/DC version, but we feel strongly about it being a major improvement over the current experience.
Thanks! What sort of better integration are you looking for? If you’d like, feel free to email me with details and I can try and find the right person for you to chat with.
Thanks! We’re excited to have you use it. If you have any feedback you’d like to share about the current experience, feel free to send me a message at mtse[at]atlassian[dot]com.
We hear you on the spacing and we ourselves are used to using Jira on wider aspect ratios. Would you be interested in a follow-up chat about how the vertical spacing impacts your use of Jira today? It would be great to have one of our designers on the call to better understand your use case. If so, please email me at mtse[at]atlassian.com and we can set up some time.
First of all, I love the passion and energy you put into your responses Greg. You’ll never hear me complain from me on reading long comments! Thank you so much for providing such rich and thoughtful feedback.
These are all very interesting suggestions and trust that I will take these to heart and bring them to our team for consideration and further discussion. Our product has grown significantly over the years and we’ve been blessed to see it used in so many beautiful and brilliant ways. It always blows my mind to see how customers are using Jira to make their work flow better. With this growth and entrance into new markets, we’ve also seen how diverse our customer base has become. Because of this, we’re often making numerous tradeoffs both locally and globally to try and please as many of our users as possible. I can emphasize with the sentiment around the People item and it’s something I will bring up to the team to see if/how we might make this better.
Regarding your comments around the Your work page and Dashboards. I completely agree that Dashboards has some amazing utility provided it’s set up correctly. Our intent with the ‘Your work’ page was to help individual contributors find and resume their work more quickly. When we shipped this ~4 months ago, we were able to see a significant uptick in this set of users getting back to their work (i.e., issues) more quickly. I know there’s a lot more we could do to make it useful for other segments. Given that this is a work in progress still, I would love to follow up with you directly about your use of Dashboards, permitted you have the time. Let me know if you’d like to chat and I’ll send you an invite.
Last but certainly not least, there really is no need to thank me for engaging with you and the rest of our customers. This is truly one of the best parts about being a product manager and something I wake up and look forward to each and every day. Thank you again for your time and commitment to us and hopefully, we can chat soon!
I appreciate the statement that "We are also putting you in control of this change. Once your instance receives the new navigation, each of your users will be able to switch over to the new navigation on their own timeframe." These changes look promising, but users still like to at least feel like they're in charge of their environment.
This is much better than the "just get used to it" approach used by certain "other" software companies (which shall remain nameless) who simply force-feed all of their "enhancements" on their users in one swoop, leaving the users either powerless to undo things, or -best case- forced to flail about and try to figure out on their own how to get their interface back to the way they want it.
241 comments