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

Customfield description show <p> tag in bulk edit - detail screen

XMLWordPrintable

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

      Summary

      Custom field description in Jira shows <p> tag in bulk edit - detail screen

      Steps to reproduce:

      • Create a JSD service desk (enable it on top an JIRA project, for example)
      • On the customer portal, raise a request.
      • Search for the issue under the project. Select and follow the JIRA Bulk Edit wizard
      • On Step 3 of 4: Operation Details, scroll to "Change Customer Request Type"

      Expected results:

      • The description is displayed without appending the "<p>" at the start / and of the description

      Actual results

      • Notice the description of the field is "<p>Holds information about which Service Desk was used to create an issue. This custom field is created programmatically. Please do not remove.</p>"

      Notes

      • The description is displayed correctly under JIRA BTF
      • The issue is not cause to JSD customfield's description, which is just plain text. The issue can be observed on some custom field like JIRA Agile "Change Developer"

      Workaround

      There is currently no workaround for this issue.

        1. BTF.png
          BTF.png
          17 kB
        2. OD.png
          OD.png
          19 kB
        3. Screen Shot 2014-10-10 at 2.22.39 PM.png
          Screen Shot 2014-10-10 at 2.22.39 PM.png
          42 kB
        4. Screenshot 2021-09-29 at 2.12.14 PM.png
          Screenshot 2021-09-29 at 2.12.14 PM.png
          272 kB

            [JSDSERVER-8446] Customfield description show <p> tag in bulk edit - detail screen

            John Smith added a comment - - edited

            JIRA Service Management Application v4.22.4

            -->
            Target start
            <span class='inline-description'><p>The targeted start date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>
             
            Target end
            <span class='inline-description'><p>The targeted end date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>

            John Smith added a comment - - edited JIRA Service Management Application v4.22.4 --> Target start <span class='inline-description'><p>The targeted start date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>   Target end <span class='inline-description'><p>The targeted end date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>

            John Smith added a comment - - edited

            Jira v8.22.2
            JIRA Service Management Application v4.22.2
            Advanced Roadmaps for Jira v8.22.2
            Jira Agile v8.22.2

             

            ---> 

             

             
            Target start Select a date
            <span class='inline-description'><p>The targeted start date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>
             
            Target end Select a date
            <span class='inline-description'><p>The targeted end date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>

            John Smith added a comment - - edited Jira v8.22.2 JIRA Service Management Application v4.22.2 Advanced Roadmaps for Jira v8.22.2 Jira Agile v8.22.2   --->      Target start  Select a date <span class='inline-description'><p>The targeted start date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>   Target end  Select a date <span class='inline-description'><p>The targeted end date. This custom field is created and required by "Advanced Roadmaps" for Jira.</p><span> - Use the dd/MMM/yy date format</span></span>

            David added a comment -

            4.20.10

            David added a comment - 4.20.10

            Jordan Wilkinson added a comment -

            @Frank as you said, that workaround makes the option to disable HTML, a security risk that is in my case, not an option, useless.

            Jordan Wilkinson added a comment - @Frank as you said, that workaround makes the option to disable HTML, a security risk that is in my case, not an option, useless.

            Frank Reitel added a comment -

            I literally posted the workarond just 4 comments ago https://jira.atlassian.com/browse/JSDSERVER-8446?focusedCommentId=2688381&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2688381

            all the Atlassian people are "inactive" so no one is picking it up and adding the workaround to the description.

            and ofc i can't mention people @atlassian

            Frank Reitel added a comment - I literally posted the workarond just 4 comments ago https://jira.atlassian.com/browse/JSDSERVER-8446?focusedCommentId=2688381&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2688381 all the Atlassian people are "inactive" so no one is picking it up and adding the workaround to the description. and ofc i can't mention people @atlassian

            Jordan Wilkinson added a comment -

            Still seeing this on 8.20/4.20

            Jordan Wilkinson added a comment - Still seeing this on 8.20/4.20

            Hossam Ahmed Mohamed added a comment - - edited

            We're facing the issue with Jira DC 8.13.18 although we've disabled the HTML in field descriptions

            Also the <p> tags showing in individual edit screen, not just the bulk edit.

            This is seen with field "Customer Notification" from the Insight plugin objects.

             

            Hossam Ahmed Mohamed added a comment - - edited We're facing the issue with Jira DC 8.13.18 although we've disabled the HTML in field descriptions Also the <p> tags showing in individual edit screen, not just the bulk edit. This is seen with field "Customer Notification" from the Insight plugin objects.  

            Daniel C Berlin (Inactive) added a comment -

            This issue is affecting us, but we also see the <p> tags showing in individual edit screen, not just the bulk edit.

            The workaround to re-enable HTML in field descriptions and list item values does make the values go away, but is not a desirable setting.

            Daniel C Berlin (Inactive) added a comment - This issue is affecting us, but we also see the <p> tags showing in individual edit screen, not just the bulk edit. The workaround to re-enable HTML in field descriptions and list item values does make the values go away, but is not a desirable setting.

            freitel_mobile added a comment -

            There is probably a workaround now for this. With https://jira.atlassian.com/browse/JRASERVER-70859 and Jira 8.7.0 there was another option introduced to "Enable HTML in field descriptions and list item values"

            this mad the HTML tags disappeared for me. 

            @Atlassian unfortunately this seems to be a default ON setting since your wrappers add the HTML tags (they are not entered in the field description) so you need to enable this option. which makes the whole option useless.

            freitel_mobile added a comment - There is probably a workaround now for this. With https://jira.atlassian.com/browse/JRASERVER-70859  and Jira 8.7.0 there was another option introduced to " Enable HTML in field descriptions and list item values " this mad the HTML tags disappeared for me.  @Atlassian unfortunately this seems to be a default ON setting since your wrappers add the HTML tags (they are not entered in the field description) so you need to enable this option. which makes the whole option useless.

            David added a comment -

            How hard is it really to fix such a simple issue. Will we see a comment issue still present in Jira 12.0 then closed as EOL for DC.

            David added a comment - How hard is it really to fix such a simple issue. Will we see a comment issue still present in Jira 12.0 then closed as EOL for DC.

              Unassigned Unassigned
              chuynhminh Chau Huynh Minh (Inactive)
              Affected customers:
              102 This affects my team
              Watchers:
              91 Start watching this issue

                Created:
                Updated:
                Resolved: