• 7
    • 10
    • 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 Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Problem Definition

      On the Portal, 'Field help' texts which are longer than two lines now appear truncated, and the customer has the option to display the full text with the 'show more' link.

      Suggested Solution

      • Allow more lines for the 'Field Help'
      • Remove "Show more" from 'Field Help'
      • Define the default behavior (expanded/collapsed)
      • Allow formatting of text in the "Field Help"

      Why this is important

      • Customers may miss the important information on field help.
        • Take "Priority" as an example, the admin would usually put the description of each priority on the Field Help and this definitely requires more than 2 lines.

        1. Capture.PNG
          Capture.PNG
          13 kB
        2. Capture2.png
          Capture2.png
          13 kB

          Form Name

            [JSDCLOUD-570] The ability to customize "Field Help" field on the Customer Portal

            Now that forms for JSM has been released (as of 17 Jan 2022) we recommend that project admins use the formatting options within a form to provide all of the necessary instructions to your help seekers.

            Forms can be found under Project Settings > Forms.  

            Simon Herd (Inactive) added a comment - Now that forms for JSM has been released (as of 17 Jan 2022) we recommend that project admins use the formatting options within a form to provide all of the necessary instructions to your help seekers. Forms can be found under Project Settings > Forms.   

            +1

            Liron added a comment -

            We appreciate the merit of this issue, but don't intend to work on it in the foreseeable future. We'll review it again within a year to see if our decision has changed.

            Thanks again,

            Liron Deutsch

            Product Manager, Jira Service Management

             

            Liron added a comment - We appreciate the merit of this issue, but don't intend to work on it in the foreseeable future. We'll review it again within a year to see if our decision has changed. Thanks again, Liron Deutsch Product Manager, Jira Service Management  

            John Smith added a comment -

            What is going on here? Somebody posting Cisco exam dumps over various Atlassian issues all over???

            John Smith added a comment - What is going on here? Somebody posting Cisco exam dumps over various Atlassian issues all over???

            Charis added a comment -

            In favor of reducing the number of custom fields (as not to degrade platform performance), we're having to co-ming one text field to answer multiple questions from the users. For that, we need to tell the users specific questions to answer which we need to show int he "Field help" section. 

            We need "Field help" to render questions like:

            1. What's the name of the project?
            2. What's the name of the project lead?
            3. question 3
            4. question 4... 

             

            but as of right now, it shows as one long line, which is hard to read. 

            Charis added a comment - In favor of reducing the number of custom fields (as not to degrade platform performance), we're having to co-ming one text field to answer multiple questions from the users. For that, we need to tell the users specific questions to answer which we need to show int he "Field help" section.  We need "Field help" to render questions like: What's the name of the project? What's the name of the project lead? question 3 question 4...    but as of right now, it shows as one long line, which is hard to read. 

            Thank you for the information trevan.householder. Please remember that each comment edit sends a notification to the watchers of this issue. Even so, I appreciate your attention to detail.

            Nathanael Motz added a comment - Thank you for the information trevan.householder . Please remember that each comment edit sends a notification to the watchers of this issue. Even so, I appreciate your attention to detail.

            I have confirmed that these also work:

            Image with a link (ignore the {}):

            {[!http://marketplace.infusionsoft.com/sites/default/files/styles/listing/public/images/logos/infusionsoft-mobile-logo-270.png!|http://www.infusionsoft.com/]}

            Image with No link (ignore the {}):

            {!http://marketplace.infusionsoft.com/sites/default/files/styles/listing/public/images/logos/infusionsoft-mobile-logo-270.png!}

            Apply image attributes (ignore the {}):

            {!http://marketplace.infusionsoft.com/sites/default/files/styles/listing/public/images/logos/infusionsoft-mobile-logo-270.png|align=right, vspace=4!}

            [~username] = Links to a user's profile
            (i) = (Information icon)
            (*) = (Standard Star icon)
            (*r) = (Red Star icon)
            (*g) = (Green Star icon)
            (*b) = (Blue Star icon)
            (*y) = (Yellow Star icon)
            (!) = (Exclamation icon)
            (-) = (Minus icon)
            (+) = (Plus icon)
            (?) = (Question mark icon)
            (/) = (Checkmark icon)
            *Emoticons* = Emoticons (strong/bold)
            ;) =
            :) =
            :( =
            :D =
            :P =
            (n) =
            (y) =
            empha[{_}]sis_ = emphasis (italicize part of the word) (ignore the [ ])
            _emphasis_ = emphasis (italicize the whole word)
            ??citation?? = citation
            -deleted- = deleted
            +underlined+ = underlined
            kg/m ^ 3 ^ = kg/m 3 (remove the spaces after and before the ^. Must have the space before the opening ^)
            Text with ~ subscript ~ = Text with subscript (remove the spaces after and before the ~. Must have the space before the opening ~)
            {{ monospaced }} = monospaced (remove the spaces before and after the word)
            {color:red}look ma, red text!{color} = look ma, red text!

            Trevan Householder_Isos-Tech-Consulting_ added a comment - - edited I have confirmed that these also work: Image with a link ( ignore the {} ): {[!http://marketplace.infusionsoft.com/sites/default/files/styles/listing/public/images/logos/infusionsoft-mobile-logo-270.png!|http://www.infusionsoft.com/]} Image with No link ( ignore the {} ): {!http://marketplace.infusionsoft.com/sites/default/files/styles/listing/public/images/logos/infusionsoft-mobile-logo-270.png!} Apply image attributes ( ignore the {} ): {!http://marketplace.infusionsoft.com/sites/default/files/styles/listing/public/images/logos/infusionsoft-mobile-logo-270.png|align=right, vspace=4!} [~username] = Links to a user's profile (i) = (Information icon) (*) = (Standard Star icon) (*r) = (Red Star icon) (*g) = (Green Star icon) (*b) = (Blue Star icon) (*y) = (Yellow Star icon) (!) = (Exclamation icon) (-) = (Minus icon) (+) = (Plus icon) (?) = (Question mark icon) (/) = (Checkmark icon) *Emoticons* = Emoticons (strong/bold) ;) = :) = :( = :D = :P = (n) = (y) = empha [{_}] sis_ = empha sis (italicize part of the word) ( ignore the [ ] ) _emphasis_ = emphasis (italicize the whole word) ??citation?? = citation -deleted- = deleted +underlined+ = underlined kg/m ^ 3 ^ = kg/m 3 (remove the spaces after and before the ^. Must have the space before the opening ^) Text with ~ subscript ~ = Text with subscript (remove the spaces after and before the ~. Must have the space before the opening ~) {{ monospaced }} = monospaced (remove the spaces before and after the word) {color:red}look ma, red text!{color} = look ma, red text!

            Andrei [errno] added a comment - - edited

            just adding to the list of confirmed working markup:

            \\ = line breaks
            (i), (!) = icons
            *bold text*
            

            Andrei [errno] added a comment - - edited just adding to the list of confirmed working markup: \\ = line breaks (i), (!) = icons *bold text*

            Hi Tim, are you able to get here a full list of what markup is supported in SD?

            Peter Bengov added a comment - Hi Tim, are you able to get here a full list of what markup is supported in SD?

            david.shilson added a comment - - edited

            Markup appears limited. Line break works fine, however the inability to do additional formatting makes the "Help and Instructions" section of the portal ugly.

            david.shilson added a comment - - edited Markup appears limited. Line break works fine, however the inability to do additional formatting makes the "Help and Instructions" section of the portal ugly.

              Unassigned Unassigned
              17c6c577eef0 julian83
              Votes:
              105 Vote for this issue
              Watchers:
              49 Start watching this issue

                Created:
                Updated: