The new jira experience is full of bugs and inefficiencies. I had it turned off, but now it looks like I'm stuck with it for good. Is that true that I can't use the old one anymore.
For me it's really awful- bad enough that i would consider dumping jira.
1- Navigation is really hard
2- The search filters are hard to get to
3- The drop downs for assigned to and for priority don't consistently work with auto fill, and clicking the dropdown doesn't always show the list either. this is the WORST of the problems.
Anyone else agree?
I do. While I can acknowledge change takes time getting used to, they have completely removed my most frequent navigation actions and added a bunch of clicks to get anything useful done. The only positive to the new UI is it seems to load a lot faster. But it's not even a Single Page Application - lots of things completely re-load the page. So I don't understand the point of the re-design.
Here are my top annoyances, in case the UI designers are reading this:
1. It has always been really hard to switch between Confluence and JIRA, and this new design did nothing to address that pain point.
2. Agile Boards are not only an extra click, but extra page load away, and I have to visually search for the tile with my board. There is also nothing in the UI that says "Board" any more, and so even realizing where to go to get back to my Board, was really hard. Thankfully, I have a link to my board saved on my Chrome Toolbar, or it would be impossible.
3. Searching is a bit better, but they took away my favorite way to search: Easy access to most recent issues. Usually I just want to see the last 10 issues I touched. "Filtering by sorting" is a common usability paradigm for users.
Update 9/4/2018: Here is a classical example of what JIRA does wrong now. They spent time promoting *slow* navigation features, and trying to tell me it's a "fast" way to navigate. What's laughable is they re-invented the Web Browser bookmark, inside JIRA, and made it worse all at the same time. Why do I need to do an extra click to access stuff important to me? ...And it's still painful to navigate to confluence.
@John Zabroski I'm a swiss army knife of IT.
What is relevant here is I lead the effort to bring Jira cloud to a ~1500 person organization. I work with multiple dev teams on their complex role based work flows. I work with the operations teams to build out multi-level service desks for support and incident management, I own the change management process which also relies on Jira, and implemented a dozen other business / support processes in different groups across our organization. Most contain screen customization's particularly using "tabs" to organize the fields in a logical way. This represents a non-trivial amount of work to document and explain the process.
When these UI changes happen it affects the non-technical end-users. Leading to a flood of calls, emails, etc.
If these new changes can respect the custom organization (or improve on it) I'd be fine with it, but to just dump all the fields on the screen in no real order, no respect for white space and scrolling, its ugly and inefficient.
Whoever came up the design should be fired. Absolutely horrible to navigate and the documentation hasn't been updated - so it's impossible to find how to do setting changes. Jira used to be an extremely easy to use piece of technology. Now it's turned to shit.
I'm relieved to see that I'm not alone in my suffering as I struggle to learn how to use Jira. I don't have the experience of using an older version; I just started recently.
The documentation is the most confusing stuff I've ever read. I'm using the Cloud version, but the documentation I've found for the Cloud version ... I just don't have the words to express how bad it is. It's almost as if it was written by 50 different people who each wrote a different part, and then threw it all together in no particular order. Every section I read uses terminology that hasn't been defined yet, and references to other sections in a willy-nilly free for all. So I'm reading the server version and that at least is somewhat organized.
Where's the step-by-step 'Getting Started' guide for new admin users who need to setup a project?
And who came up with the terminology, with names like: Software Development Issue Type Screen Scheme I can barely read it and make sense of it, let alone say it out loud to any of my co-workers. Say it three times quickly: Screen Scheme, Screen Scheme, Screen Scheme. Are they tripping, or what?
The worst thing is that I have to search the web to find tutorials written by non-Atlassian folks who have been kind enough to spend their time sharing knowledge.
Me too!!! I loved Jira before. Customizing was easy. I could set it up exactly how I wanted it. Now, I'm at a new company and I almost ready to give up. Way too complicated. You can't even shift+click a story to open the details in a new window - which I used to do ALL THE TIME. Still haven't figured out how to even enter or see the full details of a story. Absolutely hate it.
@STACEY CHRISTIANSEN I believe, on the agile board, click the card, and then hit the 'e' key on your keyboard. Use 'c' to create new issues.
You can find all the keyboard shortcuts on the bottom left hand pane, right above your avatar, there is a question mark (?) with a circle around it. Click it and pick Keyboard shortcuts. - I hope this mitigates the awful UI for you.
I hate it its really bad, everything takes now twice as much time and some things are so buggy ... its awful. Any recommendations for alternatives? If the intend of this change was to piss people off and make them to leave Jira for good well done good job
I HATE, HATE, HATE this new UI. It's SO unproductive and easy to get lost in.
I'm an Admin and I've not had one single person say they prefer it.
What the fudge are you guys playing at?
FFS - please listen to your users and revert it back or give us an option to!!!!!!
I'm just adding my two cents here as well. Initially when the changes were launched I didn't like them. Everything seemed to become harder and navigation was atrocious. As a product manager myself I sympathised and told myself I should give it some time for me to adjust. Well, it's been about 8 months and I still haven't adjusted. The navigational changes just aren't good. There is this strange context switching that occurs in and out of being within a "project" and it doesn't allow you to change easily between them. Trying to get to an advanced jql search screen (which is something I do very often and which I suspect is very common) usually takes about four clicks and page reloads from wherever you happen to be at the time when it used to take about one or two. What surprises me is that I know that Atlassian spend a lot of time on user research and interviewing. I've even taken part in one for the Jira app on mobile. So I don't understand how this design has emerged out of that process. Maybe it's just a minority who don't like it, but so far I haven't come across anyone who has!
We're officially stuck with it. See this post on February 7, 2018: https://confluence.atlassian.com/jirasoftwarecloud/introducing-your-new-jira-experience-937886012.html
It does look like they're committing to making it work - they even registered a special domain name to explain their enterprise-wide initiative, here: https://atlassian.design/
They also have a reference implementation called AtlasKit: https://atlaskit.atlassian.com/
(Tongue-in-cheek humor:) For what it's worth, there are some who might see this as pointless complaining, since they never thought JIRA was that great to begin with (hah): https://techcrunch.com/2016/12/11/death-to-jira/
Jira (and other Atlassian products) seem to have the most disorganized help of almost any product I have ever used. It is easier to do a Google search on the topic than trying to find something in Jira help.
The UI seems designed for Unix people who spend all day in the tool. It's useless and confusing for people who only occasionally use it. To be honest, I'm keeping my eye open for something easier to use and will probably change the company over when we get the time to do so.
yah we have considered dumping jira b/c of the new UI and changes to how projects are the basis for everything. our agile team board that brings together jira's from many software "projects"/products is a hot mess and not as good as the project agnostic boards. atlassian really screwed this up - they had people reverting to old jira for a long time and did nothing to fix it. everyone i work with +100's of people hates it. if it were up to me it would be gone... there has to be a better solution.
All Atlassian products are a delusion! They don't know what is UX and Usability. For any minimal change you will face huge difficulties.
All the products have basic things missing, for example, the service desk customer portal really sucks. You cannot do anything, like to add some basic fields to the user registration... So, you will support a customer and you don't know his name, because to the registration in the customer portal you can only insert the customer e-mail. Did Attlassian people thought about this tool? Did they talked with the customers about it? I don't think so...
Even for basic things you have to buy a new plugin.
I would like to know why this tools are so popular. The name for this is "status quo", but one day it finishes...
I regret all days about the decision to use this tool! Unfortunatly, now it's too late.
They're trying to save on server hardware by making us never want to use it. I tried to manage some filters today. You know, complicated stuff like edit the query. Failed utterly. I'll just use the browser's search function on the backlog.
The new Jira Cloud has done nothing but unnecessarily complicate our workflow. Between the inconsistent data validation on the time tracking fields to most things being hidden under a sub-menu somewhere. Our daily standups are slower as are our sprint planning sessions.
There are so many critical features (at least for my projects) that disappeared in the recently (maybe in August 2018) released UI. Yesterday I checked job opportunities at Atlassian to stop someone making such changes.
Really Mr. Nic Brough? Is that your answer? This product, when is in use in an organization has costs to implement, a lot! (and don't be naif to think only in the license value) To change an architecture and a business model has a big impact. After you adopt tools like Jira, JSD and Confluence your organization will be dependant on that to work in a daily basis. Clearly, you don't understand the costs involved in the transation you are proposing, from the migration to the training etc...
After that, it's the Atlassian's customers opinion that was just ignored. It's easy to understand that in other discussions in this community forum where you put questions and for years nobody from Atlassian answers to that!
It really is simple - Atlassian have stated the new UI is not optional on Cloud and there's no way back.
So your only option is to go to server.
Atlassian do read these posts, and they have recently committed to reading them a lot more. But on this topic of the new UI, they've said what's happening.
Dear Nic (Allow me that, please),
I'm aware about that. That's exactly the problem. They ignored the customers.
I know that sooner or later, in my company, we will need to move further, but we don't know if it will be with atlassian because of this and more. More? Yes, because their products don't have the basics. I have really big complains in Jira Service Desk, especially relly simple and basic details that the application don't cover. For example, you can't have details about the customers you are supporting, only their e-mail. This could be easily solved with the possibility to insert some fields in the registry form. But Attlassian is ignoring tons of topics in this community about this issue, tons of companies complaining about that. That is so basic that nobody thinks they don't have it. You always need to buy several plugins to do basic things. The plugins are not to add or improve, they are needed to the basics. The most part of plugins are only for server and not cloud.
I think to move to server it's a step back in our business model, since we don't want to maintain a server. It's part of the past, at least for us. I want a complete service.
I understand you can tell me that we should test it previously. Agree!! I admit I was naif when I decided to adopt this tools and I will pay for it!! But this is something in our company we don't allow our customers to feel. We are here to help their business and never let them feel what I feel about Atlassian.
Afterall, Atlassian is not a partner, is just a company.
Hey, Nic - less than a few weeks ago it was possible to disable the New Jira Experience. Arbitrarily telling your customer "you could go back, but we're not going to give you that chance because we decided to not" is a poor excuse.
That you are a COMMUNITY "CHAMPION"...oh, the irony.
I'm a champion because I engage with people and try to explain things, and people seem to appreciate it. Not because I work with Atlassian a lot, and certainly not because I get directly rewarded for it.
It's not me ignoring you. It's Atlassian. They're ignoring me as well, as I'm not employed by them, I'm free to express my opinion. I don't want to have a flag to enable people to switch back to the old view, I just don't want to have the option of the new one at all. It doesn't work, and I've no idea how they asked such poor questions of the users that they ended up with a dreadful UI.
In this thread, I'm just telling you how it is, and asking you to read the earlier stuff before ranting on a subject that's already been covered.
As just an normal employee in a big global company, your option of "move to server version" is out of my control...
So if you work with Atlassian, could you please tell them the summary I posted above?
I think the PO of JIRA cloud product doesn't really know how to use JIRA in details. Loosing good features is starting to affect my projects and people are starting to hate the application more.
Again, I was just telling you how it is, not that this is a good state of affairs. There is no other option than to move to a server install (or fragment and divide your users and pick other software) if you don't want to use Cloud.
And, again, They're ignoring me as well, as I'm not employed by them, I'm free to express my opinion.
As a software developer who has worked in SaaS cloud companies, and seen horror shows, usually bad cloud re-designs are due to trying to save infrastructure costs by moving to modern UIs that consume less bandwidth. It's sad, but usually the almighty dollar and cost saving is usually why such things happen.
Anyway, I sort of like it when companies like Atlassian slip up. It lets competitors jump in and steal market share. I just feel bad for those affected who are working extra hours because some third party changed things on them.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs