• 1
    • 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Whatever the original motivation for using wiki markup in JIRA, it has become clear that the software community (e.g. GitHub and even Atlassian's own Bitbucket) favors markdown syntax.

      It is extremely annoying (not to mention productivity lowering) for my students and developers (and me!) to have to switch to wiki syntax when migrating from Bitbucket issue tracking to JIRA. (I say this even though I've used JIRA with wiki syntax for many many, many years; before even using markdown syntax.) Simply put, the JIRA wiki syntax time has passed.

      Please provide us at least the option of choosing a markdown renderer in JIRA Cloud.

            [JRACLOUD-61738] JIRA Cloud support for markdown

            David Alpert added a comment - - edited

            is it possible to use the plain text markdown editor with the toggle between visual and text editor?

            as a longtime Jira user I find that the plain text markdown editor provides me much more control over the rendered description and comments than the markdown auto-formatting features do. 

            For those of you who prefer using markup languages, you can type in markdown and it will convert to fully formatted content as you go.

            this does not provide me the control I am looking for and is constantly auto-formatting my markup in ways that i do not expect

            David Alpert added a comment - - edited is it possible to use the plain text markdown editor with the toggle between visual and text editor? as a longtime Jira user I find that the plain text markdown editor provides me much more control over the rendered description and comments than the markdown auto-formatting features do.  For those of you who prefer using markup languages, you can type in markdown and it will convert to fully formatted content as you go. this does not provide me the control I am looking for and is constantly auto-formatting my markup in ways that i do not expect

            Hello,

            Great to see this is now supported within the Jira editor. However, it seems when you are exporting data to another system it still maintains the original markup for Jira. I am guessing this is converting the Markdown to the standard renderer and then displaying that. Is there anyway to have it export the text that was entered rather than the one that is converted?

            Ian Howlett added a comment - Hello, Great to see this is now supported within the Jira editor. However, it seems when you are exporting data to another system it still maintains the original markup for Jira. I am guessing this is converting the Markdown to the standard renderer and then displaying that. Is there anyway to have it export the text that was entered rather than the one that is converted?

            Nehal Jain (Inactive) added a comment - - edited

            Hi everyone,

            Thank you for commenting and voting on this ticket. In order to provide a more modern and consistent editing experience we are now supporting markdown auto-formatting across Jira, Confluence and Bitbucket Cloud in the New Jira Issue View. For anyone using multiple Atlassian products, we believe this will provide the best editing experience. Additionally, in the long term, we’re excited about opportunities this new technology will provide as we continue on our journey to helping you and your teams move work forward.

            For Jira Software users keep up to date with the New Issue View here. For Jira Service Desk users, we’ve only just started the rollout of the new issue view. Many of you will begin to see it in the next few months. You can read more about Jira Service Desk-specific changes in our documentation.

            Refer to this page to view the Markdown and Keyboard shortcuts you can now utilise.

            Regards,
            Nehal Jain
            Jira Product Management

            Nehal Jain (Inactive) added a comment - - edited Hi everyone, Thank you for commenting and voting on this ticket. In order to provide a more modern and consistent editing experience we are now supporting markdown auto-formatting across Jira, Confluence and Bitbucket Cloud in the New Jira Issue View. For anyone using multiple Atlassian products, we believe this will provide the best editing experience. Additionally, in the long term, we’re excited about opportunities this new technology will provide as we continue on our journey to helping you and your teams move work forward. For Jira Software users keep up to date with the New Issue View here . For Jira Service Desk users, we’ve only just started the rollout of the new issue view. Many of you will begin to see it in the next few months. You can read more about Jira Service Desk-specific changes in our documentation . Refer to this page to view the Markdown and Keyboard shortcuts you can now utilise. Regards, Nehal Jain Jira Product Management

            Eduardo Masiero added a comment - - edited

            Hi, everyone.

            We created a suggestion for Atlassian to provide a Plain-text Markdown (it currently has only WYSIWYG) as an option. If you're interested in that you're welcome to leave a comment/vote/watch https://jira.atlassian.com/browse/JRACLOUD-72631

            Kind Regards,

            Eduardo Masiero
            Atlassian Cloud SUpport

            Eduardo Masiero added a comment - - edited Hi, everyone. We created a suggestion for Atlassian to provide a Plain-text Markdown (it currently has only WYSIWYG) as an option. If you're interested in that you're welcome to leave a comment/vote/watch https://jira.atlassian.com/browse/JRACLOUD-72631 Kind Regards, Eduardo Masiero Atlassian Cloud SUpport

            John Rocha added a comment -

            Dear Jira,

            Add Markdown if you want, but don't take away the existing wiki markup abilities. WE don't want it. I know there are many that due but our company does not, and the community of folks I speak with do not. (I'm trying to get them to speak up, but they think this is going to be Borg'ed and we have no choice except to leave Jira).

             

            Please help the markdown community. But don't harm your markup community.

             

            Yes, people cannot believe that someone else likes the way it was because so many other tools use a different format. That's fine. Help them. Let them have markdown, but don't remove our wiki markup.

            John Rocha added a comment - Dear Jira, Add Markdown if you want, but don't take away the existing wiki markup abilities. WE don't want it. I know there are many that due but our company does not, and the community of folks I speak with do not. (I'm trying to get them to speak up, but they think this is going to be Borg'ed and we have no choice except to leave Jira).   Please help the markdown community. But don't harm your markup community.   Yes, people cannot believe that someone else likes the way it was because so many other tools use a different format. That's fine. Help them. Let them have markdown, but don't remove our wiki markup.

            Atlassian, if you ever wonder why some of your long-time users (and previously big fans and evangelists) come off as disgruntled, it's things like this. We all want Markdown support in JIRA. It's a no-brainer. There are no arguments against it. Everybody else uses Markdown. It's a huge productivity drain switching back and forth. We've been begging for this for almost two years now.

            So what do you do, Atlassian? You go and build a buggy, productivity-lowering WYSIWYG Markdown editor for Bitbucket which I'm sure far fewer people asked for (if any). See https://bitbucket.org/site/master/issues/14468 for many of its problems. It gets in the way so much that I'm just turning it off across all my instances. And we still don't have Markdown support in JIRA, e.g. when we create an issue, add comments, etc.

            Garret Wilson added a comment - Atlassian, if you ever wonder why some of your long-time users (and previously big fans and evangelists) come off as disgruntled, it's things like this. We all want Markdown support in JIRA. It's a no-brainer. There are no arguments against it. Everybody else uses Markdown. It's a huge productivity drain switching back and forth. We've been begging for this for almost two years now. So what do you do, Atlassian? You go and build a buggy, productivity-lowering WYSIWYG Markdown editor for Bitbucket which I'm sure far fewer people asked for (if any). See https://bitbucket.org/site/master/issues/14468 for many of its problems. It gets in the way so much that I'm just turning it off across all my instances. And we still don't have Markdown support in JIRA, e.g. when we create an issue, add comments, etc.

            Scott Buchanan added a comment - This is already implemented in JIRA in the new issue view: https://confluence.atlassian.com/jiracorecloud/the-new-jira-issue-view-938040503.html#ThenewJiraissueview-NewAtlassianeditor

            Hey, if you come across this feature and agree that it's needed (especially if your engineers are requesting it), then ask your engineers to come on here and vote for it.

            Kenny MacKenzie added a comment - Hey, if you come across this feature and agree that it's needed (especially if your engineers are requesting it), then ask your engineers to come on here and vote for it.

            Markdown support for comments and description fields is needed!

            Kipperlenny added a comment - Markdown support for comments and description fields is needed!

            I would like to see this as well. I write large amounts of detail into the description box. As my internet connection is not always perfect, when a connection is lost I can loose a large amount of work. Because of this I write most of my work into a local text editor and then paste it straight into description box. My favourite editor is Visual Studio Code which has a lovely Markdown editor but doesn't really understand what Jira uses.

            I would really like to be able to write markdown in visual studio code, look at the preview window it gives me and then paste it straight into Jira.

            lawrenceshort added a comment - I would like to see this as well. I write large amounts of detail into the description box. As my internet connection is not always perfect, when a connection is lost I can loose a large amount of work. Because of this I write most of my work into a local text editor and then paste it straight into description box. My favourite editor is Visual Studio Code which has a lovely Markdown editor but doesn't really understand what Jira uses. I would really like to be able to write markdown in visual studio code, look at the preview window it gives me and then paste it straight into Jira.

            John Price added a comment -

            I support a ~2000 user Jira instance and have had requests for this as well.  I agree with Dmitry above - now that Confluence uses Markdown, I am hoping you have an active backlog item to update the Jira wiki renderer to Markdown.  

            Please add this - until then seems like you have to maintain the wiki renderer code and documentation just for Jira.   Should save you some time and effort in the long run to jettison the old renderer for good.

            John Price added a comment - I support a ~2000 user Jira instance and have had requests for this as well.  I agree with Dmitry above - now that Confluence uses Markdown, I am hoping you have an active backlog item to update the Jira wiki renderer to Markdown.   Please add this - until then seems like you have to maintain the wiki renderer code and documentation just for Jira.   Should save you some time and effort in the long run to jettison the old renderer for good.

            The emperor's new clothes...new skin, but same old bones

            Deleted Account (Inactive) added a comment - - edited The emperor's new clothes...new skin, but same old bones

            As many other teams out there we are trying to make our workflow as easy, seamless and productive as possible. Markdown formatting would be one more thing to enable exactly that. Even Atlassian own engineers are in favour of this solution, so it would be great to put it somewhere on your roadmap.  

            Jędrzej Kamiński added a comment - As many other teams out there we are trying to make our workflow as easy, seamless and productive as possible. Markdown formatting would be one more thing to enable exactly that. Even Atlassian own engineers are in favour of this solution, so it would be great to put it somewhere on your roadmap.  

            Even Confluence now supports Markdown. How long until it finally lands in JIRA?

            Dmitry Stratiychuk added a comment - Even Confluence now supports Markdown. How long until it finally lands in JIRA?

            Markdown or GTFO. I will migrate my team off of JIRA, this is unacceptable. GitHub, Slack, StackOverflow, and countless tools support a variant of Markdown. It is 2018, Markdown is an accepted standard.

            Naftuli Kay added a comment - Markdown or GTFO. I will migrate my team off of JIRA, this is unacceptable. GitHub, Slack, StackOverflow, and countless tools support a variant of Markdown. It is 2018, Markdown is an accepted standard.

            We want Markdown!

            Carla Sarappa added a comment - We want Markdown!

            It's 2018 and engineers are forced to use one-off formatting tools in a ticketing system. What else is new?

            Deleted Account (Inactive) added a comment - It's 2018 and engineers are forced to use one-off formatting tools in a ticketing system. What else is new?

            lack of markdown support is inconceivable with atlassian's resources. you've made loads of money selling your product to mgmt teams, now support the users who are required to use it.

            Benny Powers added a comment - lack of markdown support is inconceivable with atlassian's resources. you've made loads of money selling your product to mgmt teams, now support the users who are required to use it.

            Any estimates when this will be available?

            I hear a lot of complaints from my team about lack of markdown support in JIRA.

            Dmitry Stratiychuk added a comment - Any estimates when this will be available? I hear a lot of complaints from my team about lack of markdown support in JIRA.

            +1

            +1 to this

            Deleted Account (Inactive) added a comment - +1 to this

            This feature is so super overdue! I can't believe we're still stuck using Wiki Renderer like it's 2006. Catch up guys! 

            Sebastian Sibelle added a comment - This feature is so super overdue! I can't believe we're still stuck using Wiki Renderer like it's 2006. Catch up guys! 

            It's been over a year and a half, and status of this still hasn't moved beyond Open?

            Vedran Opacic added a comment - It's been over a year and a half, and status of this still hasn't moved beyond Open?

            +1 for markdown! Copy and paste back and forth would be so easy

            Alessandro Gallotta added a comment - +1 for markdown! Copy and paste back and forth would be so easy

            We're trying to move from GitHub Issues to JIRA Cloud and lack of Markdown support is the #1 complaint from my engineers by a wide margin. Even if there was an expensive plugin for JIRA Cloud that could do this, we might consider paying. But I don't see one in Atlassian Marketplace, so here's my +1 plea.

             

            Phil Rzewski added a comment - We're trying to move from GitHub Issues to JIRA Cloud and lack of Markdown support is the #1 complaint from my engineers by a wide margin. Even if there was an expensive plugin for JIRA Cloud that could do this, we might consider paying. But I don't see one in Atlassian Marketplace, so here's my +1 plea.  

            +1 on this feature - using expensive plugins for markdown feature seems ridiculous.

            Russell Siachico added a comment - +1 on this feature - using expensive plugins for markdown feature seems ridiculous.

            💯 for this feature. context switching is super expensive for developers

            Micah Stubbs added a comment - 💯 for this feature. context switching is super expensive for developers

            ^^ not a duplicate, JRA-39919 is for JIRA Server

            Micah Stubbs added a comment - ^^ not a duplicate, JRA-39919 is for JIRA Server

            bmamlin added a comment -

            This duplicates JRA-39919.

            bmamlin added a comment - This duplicates  JRA-39919 .

            Or Carmi added a comment -

            +1

            Or Carmi added a comment - +1

            +1

            It's time to join the modern era Atlassian

            Paul Wheeler added a comment - +1 It's time to join the modern era Atlassian

              Unassigned Unassigned
              de93e5a1dc9a Garret Wilson
              Votes:
              163 Vote for this issue
              Watchers:
              69 Start watching this issue

                Created:
                Updated:
                Resolved: