-
Suggestion
-
Resolution: Unresolved
-
3,126
-
122
-
Hi everyone,
A brief update on this request:
For those that have provided feedback on zoom calls and the survey, thank you for your time. Its genuinely helpful and ensures we better understand your unmet needs and the impact this is having on your teamwork.
This work is not currently roadmapped, so I cannot provide a timeframe right now as to a resolution date however I will provide an update in the coming months should there be a change.
Thanks again,
Kieran Gray
Product Manager, Editor.
------------------------------------------------------------------------
Context
Since 2019 Jira is implementing a new editor (as long as a new issue view), which is composed by a WYSIWYG editor that works with markdown syntax as well. It would be great if Atlassian shipped an editor without the WYSIWYG features, where users would insert plain text markdown and would be formatted accordingly.
Bitbucket already has this feature.
Why this is important?
There can be more reasons why some users would prefer text-only editing. Including
- Improve productivity by having fewer clicks (everything would be formatted using the keyboard).
- Avoid WYSIWYG problems
- Eases the task of pasting already formatted code
Proposed Solution
- Have an option to switch from Visual (WYSIWYG) to Text Only editor
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- is related to
-
JRACLOUD-73508 Formatted "markdown" text doesn't work on the new WYSIWYG editor
-
- Closed
-
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
-
- Reviewing
-
ACE-2787 Loading...
- relates to
-
-
- Closed
-
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
-
- is blocked by
-
- Mentioned in
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-72631] Provide users with a plain text markdown editor
Hi everyone,
A brief update on this request:
For those that have provided feedback on zoom calls and the survey, thank you for your time. Its genuinely helpful and ensures we better understand your unmet needs and the impact this is having on your teamwork. Regarding repeated comments, we appreciate the strong interest here and understand this is important to many of you, but please be aware that duplicate comments doesn't increase the likelihood of this work being prioritised. Please try ensure the comments remain a valuable place for other users to review and we will ensure your feedback is incorporated.
This work is not currently roadmapped, so I cannot provide a timeframe right now as to a resolution date however I will provide an update in the coming months should there be a change.
Thanks again,
Kieran Gray
Product Manager, Editor.
All comments
Day 253 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
Day 252 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
Day 251 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
Day 250 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
Letting that sink in for a moment. That's two hundred and fifty comments left on days I was working since I started on this in January 2024. That's two hundred and fifty opportunities for Atlassian to say, "We hear you - we're planning on releasing this feature in Q3 2024." Imagine if this feature were planned in Q3 2025? Or maybe Q4? I could finally stop altogether.
The demand for a simple plain-text editor for manual markup (whether Confluence-style or markdown-style) is going to be ever-present. Don't turn customers away by continuing to leave this feature out.
Day 249 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
Day 248 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
My current thoughts on Jira cloud are just getting worse.
Having been forced to use Jia Cloud for the last few months, the feedback in general from my team is very bad....
"slow", "difficult to update", "unable to update as desired" (i.e. this bug) and more.
Our own team is now having to document details in external systems and link to jira e.g. Word, Excel docs (even sharepoint!). We are going so far backwards, it's not funny.
I suspect Atlassian are going to start to loose customers over this (and I'm sure other) bug. Please bring you're development back to developer led (which seemed to be where Atlassian came from in the first place.
Please bring this feedback to your higher ups who can make decisions.
Day 247 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.
Day 254 of commenting every (business) day until this is put into a planned release. Please give us back the feature we've had and so many are asking for.