Jira's recent update in the Jira instance at work has caused inconvenience for markup/markdown editing due to unexpected text rendering. The new WYSIWYG editor lacks intuitive interactive layout, making it unsuitable for bulk text input. To address this issue, I suggest implementing a way to toggle the old-style markup/markdown rendering while allowing users to edit markups/markdowns using external editors that support text formatting such as headers, bullet lists, and simple icons (checked/unchecked). This solution could significantly reduce user frustration when dealing with large amounts of content and enhance the overall user experience.

+1 to the growing list of people that want a way to keep the old view. There are many tickets that it's weird to see it get ignored.

@Ahmud Auleear,

 Are you seeing these comments? Please recognize that JSM admins/users/your customers are only asking for you to NOT remove something that already exists!!!  

We need the old view back as it looks like more of what a ticketing system "should" look like vs how the new view is configured.

I'm in the process of implementing Jira Service Management and it's extremely frustrating hitting one roadblock after another trying to get us what we need to run a high volume support desk.  We are literally having to customize almost every single component so it's usable for my team.

I got so excited seeing the old view in all of Atlassian's videos, articles, etc., thinking I just needed to figure out which template the old view was so I could turn it on.  Bubble completely burst when I realized they decom'd the old view.

I don't have budgeting dollars to hire a consultant, so guess who is taking lump after lump with leadership over how long this implementation is taking.  

Please allow us the option of reverting back to the old view if needed.

Please keep the old view. 

The new view does not properly handle notes made outside of Jira in an editor of choice when you copy them in.  Presumably because the markup between the old and new is different.

This is a huge interruption to workflow and productivity.

Previously, could make notes in an editor of choice with the markup on them and then copy them into Jira when done (using the old view).  Now, the same markup copied into the new view does not properly handle the formatting of the markup.  This leads to having to reformat them in the new editor which is much less convenient.

Adding lengthy notes into Jira is far easier to create them outside of Jira with the markup and then copy them in when ready.  Making the notes in Jira is not a good experience at all when they are longer.  (Quick notes... 10-ish lines or less are fine enough.... though the old view was still much better.)  

This is a negative user experience and hindrance to productivity.  Having the option to use the old view would be the ideal solution. 

At the very least.... providing the markup used in the new editor would get me by for now to still be able to create and format notes outside of Jira and bring them in later.

Please keep the old view. We have used Jira Server and were forced to switch to the cloud. My muscle memory is very good in terms of the old view. I can set our tickets up the way we like with our fields in about 10 seconds. Also, the text editor in the old view is much better. I use a Mac for Jira and very heavily use text replacements for signatures or common messages. The new view sucks and the text editor just jumbles everything together when I use text replacements. I would like the setting back to turn on the old view indefinitely. 

What is the status as the old view states it is going away in January 2023?  January ends next week.  WTF is the deal? Im furious.  

Scrolling through pages of irrelevant fields to find pertinent information is a huge step backwards from server to cloud.  As a consumer, the fact that this issue has been reported since 2019 and Atlassian still took away the ability to disable Jira labs speaks volumes.  Forcing your customers to find a workaround such as disabling the view on each individual issue, or using a chrome plugin, is not a sustainable option for large organizations.

Tools are meant to enhance productivity and this is a major oversight as to how your customers are using your product. Please bring back the old view or at the very least give your customers the choice.  

Anyone else find it interesting that they are taking away the old view for customers but their tickets are still using it...

I like the part where I can use mark-up in order to make comment reviews more human-readable friendly by tabbing, indenting, and color-coding, but then the NewView™ hides/ignores... some? of that mark-up... but not always? So then you're hunting through existing comments trying to figure out how to fool the NewView™ into obeying the mark-up.

Unless if you use the old view. Then it's all displayed exactly as you want it.

But people should stop using the old view that just works. The old view is called "old" and that means shameful and bad, and you should feel bad for liking it and advocating for it.

Just because NewView™ is capricious and a headache, doesn't mean it's bad. It was merely released too early and needs to be sent back to beta for more testing.

In conclusion "?oldIssueView=true for President"