Hey Jira can you keep the old pull-request view please? Tried the new view for a month to see if I could get use to it.
The new view is awful. It's hard to find anything and it's terrible to navigate. If you have long file directories, you can not see the complete paths on the right panel, rendering it completely useless. At least keep the file change list at the top of the MAIN panel, so you know, we can actually see the file paths/names.
If we are forced to used the new view, we will move to another platform.
Or find someway to "Compress" the file paths so you can actually see the changed file. Having the list of files at the top (old view) is really nice. Maybe just put the old view file list into a div that has a max-height and make it scrollable if you really want more space for the code changes. Then you could remove the right panel.
This mandatory switch to the new "view" (really wonder what UI/UX-designer is responible for such a mess) is the worst move I personally have experienced with Atlassian. At least give the people a choice and do`nt traet them like idiots!!! For me this is a trigger to evaluate another system.
That's it folks, in week's time we won't even be able to use the old UI anymore, and Atlassian doesn't care one bit.
The new UI breaks backward compatibility with tables, which we used a lot, and support doesn't even respond.
And the we get solicited for feedback, do they really care what we say?
Like many others here, who has used Jira almost from day 1, I feel abandoned.
Way to go Atlassian.
Jira Settings | Default user preferences (under user interface)
Does not have an option for this, so I doubt that you'd be able to set this globally.
You'd have to ask Atlassian for that.
Good luck, seeing how this was shoved on us, and probably soon we won't even be able to go back to the more useful older Issue View and be forced to accept the new Issue View with all it's limitations.
Remember, you must keep talking about this in various places. Without mass 'outcry' about it, the atlassian product team shows all signs of taking away the ability to revert — out of some hubris that we are all 'too fussy' and 'need to give it up'.
Also, it's wrong that admins cannot give their teams the defaults that are preferred.
I had feedback bubble-up from multiple teams that 'people hated jira' and were asking we migrate to other tools. Think about the time lost: all of those people dissatisfied at work, and researching other tools to replace the crappy jira experience they were now having. Then taking the time to talk about it as a team and bubble-up the feedback. All because of this hubris from Jira Product team.
Couldn't agree with you more @Zachary Jones , so pleased that for the moment there is the feature to turn off the new view. Makes you wonder who in the management structure decided it was a good idea to try to force people to the new view?
Surely if they are the experts they say they are in agile development they would have at least heard of canary releasing? Blue / Green testing? Community reviews?
I will keep making noise about the new view in other forums to hopefully make sure the new view isn't the only choice.
Same here. The new view is missing one key item. The Development widget from the bitbucket-jira integration.
This new view has made me add one additional step to working with ticket.
Is not new things supposed to make life easier.
As with others, I will push for an action to move away from Jira. I am sure we can find another product that is actually listing to customer feedback instead of trying to push new and "better" things without regard.
Here's a tampermonkey script that does it for you, I fear that this will not last very long before Atlassian removes that query parameter, (typical Atlassian way of looking after customers).
// @name Jira, load old view
// @version 0.1
// @description Load Old jira view
// @author Unhappy Atlassian Customer
// @match https://*.atlassian.net/*
// @icon data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
// @run-at document-start
// @grant none
var loc = location.href;
if (loc.indexOf('oldIssueView') >= 0) return;
loc.indexOf("?") < 0 ? (location.href = loc+"?oldIssueView=true") : (location.href = loc+"&oldIssueView=true");
There is a workaround (of sorts). In the upper-right corner you can click the button with the three dots. One of the resulting options is to view the issue in the old view. Unfortunately it seems that this must be done on each individual issue. I have no idea if it works on anything other than the items themselves.
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