I hate the description field wysiwyg editor. Why does Atlassian hate Markup? Can't you add a Markup Plugin Module to the + drop-down menu? Then everyone can be happy.
The new view is terrible. None of the information I use is in the main display area, the spacing is all off with too much whitespace, and most importantly, there is no EDIT button! I always use the Edit button because I can update multiple fields at once and then it is cataloged as ONE item under the History log, making it much cleaner and easier to read. Please add the EDIT button to the new view!
First you force everyone to go to cloud and now you force people to use new view which they also don't want to use (especially if since many years they were working on server version).....
Don't like the new view. I have already expressed my dissatisfaction with the Jira team not listening to people's comments. The new view is extremely slow, editing the descriptions is horrible, it doesn't allow to edit several fields simultaneously. These are just few from many problems with the new view.
Unfortunately, we are using the new view. I have to switch to the old view every time so that I can jump from there to the issue in the agile board.
Please add the menu item to the new view! There has been a ticket for this for a long time (since 2018) and many people (until today 138) have voted for it:
My biggest issue is the inability to log work accurately. This is major problem for us, you can't specify the time piece of the "Date started" don anything other than 30 minute increment. We need to be able to specify it accurately. You CAN when you mark a task as DONE, but that only gives the user the one short and assumes they only work on a task once.
The second issue that drives me nuts is if you are in the new view and you need to delete a task; you have to click on the task, click delete...and then it takes you back to the top level board, NOT the parent story. Very frustrating.
The new view renders many of our existing tickets almost unreadable! We often have many attachments and refer to them as links in our descriptions and comments. The new view turns all of these links into thumbnails, which works horribly when used inline in a sentence. We have thousands of existing tickets like this.
For comparison (and this is only the start of that ticket's decription):
Apart from references to attachments being too fancy (see post above), references to other issues are also very elaborate, which can make descriptions with many references to other issues very hard to read.
It would really help a lot if there is an option to display just the issue key instead of the "key, summary, status" thing everywhere.
@Karen Rabalais I found the solution to changing issue types after some research: You need to click the little issue type icon (for example by default the little blue checkmark-icon on tasks) to change your ticket to a different type.
Does anyone know how to assign an issue with a screen mask in the new view? It annoys me heavily that assigning and commenting at the same time is always a 2-step process, probably triggering multiple emails. I loved being able to assign without status change in the old view while simultaneously adding a comment.
I have a lot of hidden custom fields running on background. I only use old view to access the "edit" buttom, from there I can see all hidden fields. If you remove that, how am I work on hidden fields?
Based on the Atlassian team's response on JRACLOUD-72631 (TLDR: "we hear you but we don't respect you and will not address your request") it is clear that the plan for JIRA cloud, going forward, involves ignoring any negative user feedback because it interferes with the long-term project plan to declutter the UI by removing all useful functionality.
I will be strongly recommending to anyone I know in the industry to avoid Atlassian cloud products. When we were on JIRA server sure, it was a pain that we had to support it ourselves, but at least we weren't locked into using the current version of a product which is developed by people who justify their salaries by breaking it on purpose.
There's still no way to reference an existing attachment in the "new view". This is pretty basic functionality. I don't know how you could even consider removing this "old view" without this.
The new view seems to be designed for people with monitors that are vertical with fields that you have to pin, that often requires redoing, such as "requested participant". Majority of my team that use various data fields agree that the old view is more intuitive and less buggy. It is truly unfortunate that you are getting rid of it. Sad day for Jira.
In the new view, we do not have the option to search and link issues using JQL eg. I do not get the option when i want to link backlog items to a release ticket. This feature helped me link multiple backlog items at once just by filtering them using JQL. Could you please add this feature back?
Raised by multiple people many times, but I still don't see Rank to top and Rank to bottom options in the new view. This is now the only reason I still rely on the old view. Please add these options before turning off the old view!
One of our jira projects uses mark down heavily to create stories. With the new jira view for whatever reason not all of the mark down are supported. I constantly have to switch back to the old jira view in order for everything to be displayed properly.
We have over 500 stories created using mark down. Once the old view is no longer accessible these stories won't be displayed properly to us anymore. Ugh.
255 comments