At the moment, this is not an option that a Jira Cloud site-admin would have the ability to change for all your users through the web console. It still might be possible for our Cloud support team to disable this new feature on your instance. However I would recommend opening a support case in order to do this. You can do so at https://getsupport.atlassian.com
I am not sure if you can still do this today. I know it was possible at one time. There may come a time when it is no longer possible to turn this feature off.
We experience challenges as the new UI has fields on it that we have chosen not to enable. The "New UI" overrides those field settings and causes issue with users and support within our teams.
Example: "Time Tracking" is a field we don't want to enable. Our field screen layout doesn't have it but if the users click on the new ui option the field shows up.
I'm jumping on the band wagon here. We have carefully groomed the views to minimize clutter, be consistent across projects and shift commonly used information to the top. This setting completely undermines the administrative design. Our user's hate the views and there needs to be a way to turn them off at an admin level or at least they should be disabled by default for all non-next gen projects.
@Andy Heinzer is this available yet? The new interface where all the ticket details are squeezed off to the side is unusable. Getting a little fed up of clients and team-members complaining about this - how do I disable it as standard? Otherwise I think we are going to have to look at a different tool that has the flexibility of the old JIRA
I think you might be referring to something slightly different than the original post. I believe you are talking about the new issue details view on a Scrum or Kanban board. If that is the case, there is a Jira Labs feature that you can currently disable this specific new feature. To do this go into your user avatar -> Personal settings. On that page there is an option to disable this new issue details view there.
Thanks for getting back to me Andrew. I didnt mean specifically in relation to the scrum board - we use a lot of custom fields for the scrum board is just for an overview and the backlog view doesn't give enough detail - so we generally look at the full version of an issue. This is where we are finding that all the information we actually need is squeezed off to the side and really stretched up (because the details of the ticket are at least a few multi-line fields) and the vast majority of the screen estate is given over to comments.
I can see how maybe this would be good if you had a workflow that required lots of back-and-forth on tickets - but this isn't my experience in software development - so it's quite an obstructive change for us. Also - never hurts to let people make their own decisions :)
Why no one from Atlassian is responding to such requests? They introduce a new "LAB" feature (which is really not usable right now) and give Administrators no option to disable it for the users - and make it default!
There is right now no way to configure the order of the fields of the new view on a central place, so I have to configure it for XXX projects by hand! Before that is not solved, they cannot force organizations to use it!
Lol. They can do anything they want and that is exactly what they are doing. What are you gonna do? Convince your boss to switch to some other platform?
But I hear you. I am in the same predicament.
They turned an opt-in lab feature into an opt-out feature without letting Admins (and thus entire organizations) control it.
This is, I think, by design on their part. Rather than talk to their customers and get use case data (as is common place good policy in the software design world) they are abusing "agile" methodologies by forcing various JIRA-using organizations to use the new issue view (I suppose to SLOWLY get feedback to fix what is broken) and then getting feedback to fix what they broke - and there is a LOT broken that should have been obvious to them in hindsight. In this way they can slowly transition JIRA into a golden new age without getting a deluge of super angry customers - just using random customers as guinea pigs to get the job complete. Not what the founding fathers of Agile were expecting.
This is of course just my angry paranoid opinion derived from two facts:
1) The complaints about the new issue view are strangely spread out over a year-long or more period (instead of a sudden onslaught of them).
2) The new issue view is so bad that there WOULD be a deluge of angry customers if they flpped the switch on everyone at once.
It´s really unbelievable...
Atlassian has become an overbearing and ignorant f****** company. Too bad.
It's simply how it is. Evolution. Companies come and companies go. And most of the blame is bad management and customers are ignored. It will make someone better.
I’ve been a Jira user for about 15 years and I’ve had my fair share of swearing configuring Jira, and had to clean up a few overengineered installations but still held Jira high, it’s always done its job even if it sometimes were very slow.
Having been out of the loop for a few years I’ve recently taken the CTO position at a company very focused on Microsofts products and have become very frustrated with the Azure Devops (VSTS/TFS whatever) for product development planning/Scrum tool, and since we’re using Jira Service Desk I ”knew” that it would be a breeze to replace Devops with Jira and get a much more efficient way of working and solve a few of our problems (the ones solvable by a product anyway).
Boy, I was mistaken.
I personally sat down to help with setting up the instance and add a few configurations I know we need, but was absolutely baffled by the constant clicking and that you seem to get lost between the semi-new agile project board UI and the older issue view (not to mention next-gen, that is potentially the crappiest excuse for a MVP released to the public I’ve ever seen, why in the name of anything holy would I pay for enterprise-grade and getting something like that).
I understand the need to refresh the UI, it wasn’t the best as some people say, but you can’t release something like that (unfinished, lacking efficiency, and counter-intuitive) with the feedback given and then start releasing the trello-like ”NextGen” without understaning it will, eventually, make the company become irrelevant.
I’ve seen this trend in other places as well, AWS new interfaces are becoming more click-intense and other major players realize their UI’s looks old and clunky. But mind you, the perhaps most efficient UI for systems are green text on black background. Not beautiful, not easy to learn, perhaps not easy to sell, but efficient as hell. And we’re investing in efficiency.
With this new UI, you’ve unfortunately and effectively moved yourself to a position behind Microsoft, even if Azure DevOps has a long way to go to become what you were.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events