Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-554

Rich text editor functionality for Customer Portal in JIRA Service Desk

    • 56
    • 10
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Currently, there are customers who are using JEditor - Rich Text Editor third-party plugin for JIRA itself. However this third-party plugin does not support JIRA Service Desk. It would be best if we can provide alternative methods for rich text editor for customer portal in JIRA Service Desk as well.

          Form Name

            [JSDSERVER-554] Rich text editor functionality for Customer Portal in JIRA Service Desk

            This is yet another common-sense feature that is missing. However, as long as there is a vendor in the Marketplace selling a plugin that provides a feature,, Atlassian will never implement it. Why should they? They collect passive income from their cut of the add-on sales, plus they don't have to develop or maintain any new code. I guess you could think of it as an evil twist on the concept of open source. Other people make all the needed enhancements, but since it's closed-source, nothing gets put into the core product and everything has a price tag.

            Jerel Crosland added a comment - This is yet another common-sense feature that is missing. However, as long as there is a vendor in the Marketplace selling a plugin that provides a feature,, Atlassian will never implement it. Why should they? They collect passive income from their cut of the add-on sales, plus they don't have to develop or maintain any new code. I guess you could think of it as an evil twist on the concept of open source. Other people make all the needed enhancements, but since it's closed-source, nothing gets put into the core product and everything has a price tag.

            Carol Jones added a comment - and JSDSERVER-4970

            See also JSDSERVER-1506

            Majken Connor added a comment - See also JSDSERVER-1506

            farshadm added a comment -

            JEditor works OK in customer portal. Make sure you enable the related modules first which are disabled by default.

            farshadm added a comment - JEditor works OK in customer portal. Make sure you enable the related modules first which are disabled by default.

            JEditor isn't working for me in the portal. All I get is a wiki renderer.

            Karen Mixon added a comment - JEditor isn't working for me in the portal. All I get is a wiki renderer.

            Confirmed - JEditor works fine in the Customer Portal.

            Wolfgang Fellner added a comment - Confirmed - JEditor works fine in the Customer Portal.

            Peter added a comment -

            Can someone confirm that JEditor work in exposing a Rich Text editor to customers?  Does it interfere with the new native JIRA visual editor?

            Peter added a comment - Can someone confirm that JEditor work in exposing a Rich Text editor to customers?  Does it interfere with the new native JIRA visual editor?

            When it is enabled, doesn't it appear in the Customer Portal for the comments field in existing requests?

            Justin Alex Paramanandan added a comment - When it is enabled, doesn't it appear in the Customer Portal for the comments field in existing requests?

            Same as u

            Luciana Cagnetta added a comment - Same as u

            luciana.cagnetta544343408, what do you see in your JEditor Configuration > Service Desk screen?

            Justin Alex Paramanandan added a comment - luciana.cagnetta544343408 , what do you see in your  JEditor Configuration > Service Desk screen?

            It's a  big lack of functionality on the customer portal, I even tried installing JEditor and activate it as in Justin Alex [ServiceRocket]  attachment, but it doesn't work. Moreover there's no documentation regarding it

            Luciana Cagnetta added a comment - It's a  big lack of functionality on the customer portal, I even tried installing JEditor and activate it as in  Justin Alex [ServiceRocket]   attachment, but it doesn't work. Moreover there's no documentation regarding it

            itay added a comment -

            I am also facing the same issues.

            itay added a comment - I am also facing the same issues.

            yes but the problem with this JEditor addon is that it is unstable : I don't recommend it for Production now.

            I faced problems with it on some JIRA instance : js script broken, error on page loading, etc etc

            Damien (darwyn) added a comment - yes but the problem with this JEditor addon is that it is unstable : I don't recommend it for Production now. I faced problems with it on some JIRA instance : js script broken, error on page loading, etc etc

            Seems to me that JEditor has the option to set the Description, Comment and Environment/s field to have the rich text editor panel enabled:

            Justin Alex Paramanandan added a comment - Seems to me that JEditor has the option to set the Description, Comment and Environment/s field to have the rich text editor panel enabled:

            please allow the rich text editor feature in the JIRA Service Desk Portal, it's a must have for all our customers.

            Damien (darwyn) added a comment - please allow the rich text editor feature in the JIRA Service Desk Portal, it's a must have for all our customers.

            Description field with JEditor renderer works well on my side, while comment of a service desk jira project is always with wiki renderer when JEditor has been un-installed and text renderer is been used by the comment field.

            Believe it is a bug of service desk. Please investigate.

            Cheers
            Hailin

            Hailin Zhang added a comment - Description field with JEditor renderer works well on my side, while comment of a service desk jira project is always with wiki renderer when JEditor has been un-installed and text renderer is been used by the comment field. Believe it is a bug of service desk. Please investigate. Cheers Hailin

            IT added a comment - - edited

            While the JIRA equivalent to this https://jira.atlassian.com/browse/JRA-8943 has over 300 votes, I think this one is actually a higher priority because JIRA Service Desk is essentially an email client. What email client nowadays has no rich text editor? Even the basics (bullet points, link, bold) would be a dramatic help. Furthermore, standard JIRA has add-ons available to solve the problem - like JEditor. But unfortunately JEditor is NOT compatible with JIRA Service Desk... I can't expect to train all of my staff on a new mark-up language.

            This is our #1 issue with Service Desk (now that the pricing model has been fixed).

            IT added a comment - - edited While the JIRA equivalent to this https://jira.atlassian.com/browse/JRA-8943 has over 300 votes, I think this one is actually a higher priority because JIRA Service Desk is essentially an email client. What email client nowadays has no rich text editor? Even the basics (bullet points, link, bold) would be a dramatic help. Furthermore, standard JIRA has add-ons available to solve the problem - like JEditor. But unfortunately JEditor is NOT compatible with JIRA Service Desk... I can't expect to train all of my staff on a new mark-up language. This is our #1 issue with Service Desk (now that the pricing model has been fixed).

            This issue is a major drawback for customers used to Confluence, Confluence Questions or other helpdesk software. Our customers are used to copy&paste images (e.g. screenshots) directly into the service request. Having them save the screenshot first as an image and then attach it to the request is a no go. Sorry... I already filed an issue at JEditor, asking for Service Desk support.

            Jan-Peter Rusch added a comment - This issue is a major drawback for customers used to Confluence, Confluence Questions or other helpdesk software. Our customers are used to copy&paste images (e.g. screenshots) directly into the service request. Having them save the screenshot first as an image and then attach it to the request is a no go. Sorry... I already filed an issue at JEditor, asking for Service Desk support.

              ashubovych moofoo (Inactive)
              dchua Daryl Chuah (Inactive)
              Votes:
              146 Vote for this issue
              Watchers:
              76 Start watching this issue

                Created:
                Updated:
                Resolved: