Why is it you can't just leave the old view available as is? Make your changes to the new view and maybe we'll switch some day, but for now, leave the old view alone and available.
The critical flaw I see is not that they want to create a new view, that is fine. But how can they create this new view that does not allow users to customize it to match the view they had already created that worked perfectly to suit our needs? We tried the suggestions. It STILL requires us to navigate to multiple locations to get all of the info we can now get in one place. As a software company ourselves we are well aware that Backwards Compatibility is a MUST for all upgrades. Why would we want to force our customers to adapt and change when it is unnecessary? They pay us money annually (As we do for Jira) and it should be our goal to allow them to use our software in the same method they have been using it without having to become MORE inefficient and unhappy. This would lead us to become a Former software company pretty quickly.
Although we suppose old issue view would be end in the future, we still need old issue view as we are currently migrating to cloud.
When you stop old issue view function, please take long time after you announce this information in order to change user's daily operation. Otherwise many users cannot continue business as usual.
On the old view one can select all the assignment groups from the group icon which isn't visible on the new view, 1 would have to know the exact spelling and case then type it as is to find the required group
When will this functionality be added to the new view?
thank you for your recommendations, but the main problem for me (and I'm not the only one, as I can see from the comments) is the unusable WYSIWYG editor.
Can't you re-add the nice old markdown/markup editor to the new view ?
Hi Required Old view it is easy to understand for processing and we are easy copy and paste comments so pls either continue old View or give option for old view
most of the time you read/copy from the description, not edit it.
why does double clicking a word in the description of a ticket causes to edit it instead of selecting it so i could copy-paste it like any other place in the ticket? this is a horrible UX.
I would like to think that the folks at Atlassian actually care about what we say here, but I'm pretty sure that's not the case. Having said that, the new view is not user-friendly, it's harder to find things, it takes me 30% longer per Jira to understand where things stand, and many of the important fields I need for my day to day are not shown and now I have to go and track them down. Bottom line: you "new" UI looks like the 1990s and acts similarly - I wish you wouldn't make changes just for the sake of changing...
It is obvious that you just want to add some innovations, even if they are bad decisions, at any cost!!!
...one of the problems - It takes longer to load a page!!! Activity - Show: All [Comments + History + Work log] ...whay "Load more"? Let us see everything with one click? Without wasting time on "Load more"+"Load more"+"Load more"+"Load more"...!!!
The 'New view' has much worse user experience when working with issues comparing with the Old one:
* 'Edit issue' widget is not available anymore
* 'Action' widget for subtasks has gone
* Time estimated/remaining for subtasks has gone
In the Old view you had possibility to work with issues/subtasks without moving away from the main issue screen. With the "New' one you have to open new browser tab for each action in order to keep the main issue - what kind of 'improvement' is that? :(
The new view is clearly optimized for mobile first, and unfortunately also only.
For tickets with big code blocks to be manageable, you need to allow us to: 1. set the width of the ticket to take the whole screen - to reduce side scrolling.
2. (allow to) limit the code blocks height and be vertically scrollable, so that length code blocks won't require scrolling the whole page forever to get to some comment.
New view does not have markdown editor. Why is that? For most tickets I have to write a table listing deliverables, versions and instructions. The process is pretty quick because I have a markdown template prepared. With the new what-you-see-is-all-you-get editor this requires creating a new table from scratch every time!
I only use the OLD VIEW for one click highlighting the fields so I can copy them. The new view doesn't allow this. Also you can't use the coded WYSIWIG editor when typing, you have to click click click click click emoticons manually that take hours (per year) to do. Where as before I can just type (/) (!) (x).. The edit button is right there!
I had to use the old view recently because I wanted to restore a previous version of a ticket.
With the old view, I can cut and paste a previous version of the ticket that is stored in the history in the source Jira markup format (with markup such as {label...}).
Unless there is either:
a proper way to use the history of the issue and to restore previous description
Please can you allow negative story points to be entered using the new view? I am having to switch to the old view to enter negative story points currently.
255 comments