-
Suggestion
-
Resolution: Fixed
-
None
-
6
-
6
-
Hello,
Thank you for bringing to our attention the request to maintain both a legacy experience and a new experience. We understand your desire for continuity.
We are committed to continuously improving it based on user feedback. The new issue view’s unique value has always been its immense customizability. Every team has different needs, including yours, and teams using the old issue view can’t personalize it. In the new issue view, admins can configure which fields are on the left, and which are on the right.
Maintaining two issue views would have slowed us down from our north star: to make the new issue view the best for every team, including yours. By cutting down to one issue view, we’ll be able to fix bugs and ship features faster.
I'll be closing this ticket down, but please add feedback to feature requests on Issue- View as as we actively review and use the tickets in our prioritisation process.
Thank you for your understanding and continued support.
Ahmud
Product Manager- Jira Cloud
I, as JIRA user, would like to be able to disable the new issue view.
- duplicates
-
- Closed
[JRACLOUD-68905] Ability to Disable New Issue View
The way Atlassian is dealing with user feedback makes me sick!
We know that the new issue view isn’t everyone’s preferred option, but our goal is to make it so.
We know Atlassian loves the new issue view, but as your customers our goal is to keep the old view.
You cannot maintain two view because you are a small company with not much technical staff? Ok, then keep the OLD ONE as requested. You are dealing with adults, not kids! What the f*'# is wrong with you?
The new view is not new, its been out a long time, I guess you mean the current view.
My feeling is Atlassian won't ever provide a way to disable the new view. But it is frustrating that they do not seem to be listening to customer feedback about the new view either.
In our Server to Cloud migration we have encountered many bugs and issues with the new view.
JRACLOUD-72208- no easy way to insert existing image attachment into a comment/description- JRACLOUD-74347, JRACLOUD-47677 - too much white-space around inline images.
- JRACLOUD-76714 - cannot drag & drop attachments
- JRACLOUD-76578 - the parent issue type & epic name are not displayed on company-managed projects.
- JRACLOUD-67884, JRACLOUD-69044, JRACLOUD-75406 - wasted white-space on the sides of the new view
JRACLOUD-73428, JRACLOUD-72742 - the UI to assign and add a comment has been removed.JRACLOUD-79715- screen space is wasted by always showing the add comment field.JRACLOUD-78268- the description field's clickable area doesn't match the visible border- JRACLOUD-76424 - no tool tips are provided for issue states, and the view workflow screen doesn't show these either - how are users to learn the sometimes nuanced meaning of states if Jira doesn't show them?
JRACLOUD-79715- increasing the width of the issue detail sidebar doesn't really help users see more.JRACLOUD-77611, JRACLOUD-75855,JRACLOUD-78371- sometimes issue references don't turn into links.JRACLOUD-73516- the issue type name is no longer displayed! Not tablet friendly.JRACLOUD-75181- only one workflow transition button is 'always' visible - so more clicks are required to transition issues.JRACLOUD-76318, JRACLOUD-73196 - only some comments are loaded; and there is no option to disable this. Painful when you want to search comments inside an issue.- The issue detail view on agile boards now uses the project field configuration; instead of detail fields selected in board configuration. This results in a cluttered issue detail sidebar.
- Many issues with rich-text migrated from Server not being rendered correctly in Cloud (cannot find JAC issues for these defects) including:
- Images inside quote block break the quote
- Heading immediately following a table or list
- Table inside or immediately after a list
A couple of these are getting attention but it is taking a long time to deliver a solution. In most cases it seems Atlassian is ignoring customer feedback.
Well it is like more than a year there is bug reports with new view which are impacting us and our users, all has been reported. Non is fixed, thus I vote for old view which does not have those bugs.
If they could just add Rank to Top or Bottom in the new Issue View, I would remove my vote. But they haven't done that for the past years, so Atlassian does not seem to listen to their customers.
As of now, we don't find it as effective it need to be. We as a Jira admin want to disable it for our users as in bulk (global settings)
Guys this should be a TOP PRIORITY! Why do you even implement a new issue view when you can't even translate some common functionalities to it?! And you even prevent people from switching back to the old?? This makes no sense guys.