How to switch between 'Visual' and 'Text' mode of Issue description in Jira cloud?

[Tom Austine]

Issues in my project, when viewed full-screen mode, show all the wiki markup syntax when you put the issue description in edit-mode. On Jira server you used to be able to switch between 'Visual' and 'Text' modes to hide/show the markup.

This however doesn't occur when putting the description of an issue in edit mode, when viewing the issue in the side panel on a Board.

Any ideas?

[dmitry_popov]

That is really disgusting that I can not use the markup instead of the visual editor in Jira Cloud.
For example, I cannot set a non-standard text color (i.e. apart from those colors that are present in the color-selector), which is critical when describing, for example, the css styles.

Please return the text editor! That was perfectly working for years (at least for local Jira installations).

[Timo Toivonen]

Please bring back the text-edit view. It is the most useful feature.

[Joe Matazzoni]

If Jira is going to hide the text-edit view, please Atlassian folks, fix your editing bar so that it floats with the window as the user scrolls down. When I write a long ticket, I now have to scroll ALL the way up to the top to do something like change color or apply a heading level.

That is a very bad UX

[Alexey Matveev _Appfire_]

Hello,

Do you mean that you do not have the Visual and Text options in Jira Cloud? If so, then it is the correct behaviour. You use the old issue view. You should use the new issue view.

[Tom Austine]

Hello, I wanted to know how you switch between Visual and Text in Jira Cloud, not if it behaves the same as the server version.

My problem is that when I go to edit a description, the text is all marked up (wiki markup), and there is no option to hide the markup and show the formatted version.

[Alexey Matveev _Appfire_]

You can not switch between Visual and Text in Cloud. Cloud behaves differently from Server.

[Tom Austine]

So how do I 'hide' the wiki markup then? Do I have to apply a different view or something?

[Alexey Matveev _Appfire_]

You need to use the New Issue View. You will not be able to see the markup codes there. The New Issue View is set by default:

New Issue view is available from boards:

[Tom Austine]

Thanks @Alexey Matveev _Appfire_  can the 'new issue view' be applied to issues when they are not viewed from a board?

[Tom Austine]

Here is an example:

Description field in view mode:

Description field in edit mode:

As you can see, when the Description field is in edit mode, the markup syntax is shown.

[Alexey Matveev _Appfire_]

You can not switch the new Issue View on, where the old issue view is shown. 

[Tom Austine]

Yeah so I've confirmed that I'm using a 'classic' project, which would explain why the New Issue view isn't on. So why does the description field show markup when in full screen mode, and not when viewing an issue on a board?

[Alexey Matveev _Appfire_]

When you view on the board, you use the New Issue View

[Tom Austine]

Ok so there’s  no way to hide/turn off the markup (so it renders like the new issue view) when viewing an issue in full screen mode for a classic project?

[Tiffany Stull]

The WYSIWYG editor does NOT provide the same amount of control that editing in Jira markup allows.  For example, if I want to create a numbered list with a bulleted sub-list, that can only be done via markup.  This capability is essential when I'm creating a list of testing steps that also includes multiple selections beneath a step.  Example:

# Select the link to this page.
# Select the following checkboxes:
** Item 1
** Item 2

I'm able to create new jiras in Jira cloud with markup.  Why can't I edit existing jira descriptions or other fields using markup?

If Atlassian is removing the markup editing capability, the WYSIWYG editor needs to be improved so it will support all functionality that exists when writing descriptions using markup.

[Ian Wermerling]

I have the opposite frustration because I like the WYSIWYG view for some of my stakeholders, but they have to see their content in markup when they first create the ticket.

Consistency between create and view would be good, as well as the option to use either WYSIWYG or markup on both you be good to see to.

btw I'm using cloud.

[Manabu Tokunaga]

I would also like the "New Issue" Editor to be *not* stuck in Markup. I use Markup in README.MD but for a good chunk of non-coders like PMs and CEOs that won't go over very well.  Personally, also for quick edits of an issue, it's better not to be Markup.

[s_kudal]

Hello All,

I've a question about "Custom Fields". I want a field just like "Description" which has format panel on the top side. But there is only "Text Field" which I can add. But this is not just like "Description" field. Its is only an empty free-text field. There is no any formatting panel (which allows us to change the style and widht of the writings)... Is there any alternative way to do so?

Thank you