Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-20055

select list customfieldvalues not being encoded when exported to xml, this causes the JIra issues macro to fail.

    XMLWordPrintable

Details

    Description

      When you have customfields with utf-8 characters, for example Dérivés, then in the xml file that is created:

      E.g. http://localhost:8080/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?query=Donner+AND+GP+&summary=true&tempMax=1000

      We see the following:

                     </customfield>
                                                <customfield id="customfield_10083" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                    <customfieldname>P&#233;rim&#232;tre</customfieldname>
                    <customfieldvalues>

                        <customfieldvalue><![CDATA[Dérivés]]></customfieldvalue>

                    </customfieldvalues>

      The value is wrapped in CDATA and not encoded.

      This causes confluence jiraissues macro to throw 

      java.io.IOException: Error on line 2433: Invalid byte 2 of 3-byte UTF-8 sequence.
        at com.atlassian.confluence.extra.jira.DefaultJiraIssuesManager.getChannelElement(DefaultJiraIssuesManager.java:163)
        at com.atlassian.confluence.extra.jira.DefaultJiraIssuesManager.retrieveXML(DefaultJiraIssuesManager.java:192)
        at com.atlassian.confluence.extra.jira.JiraIssuesServlet.getResultJson(JiraIssuesServlet.java:165)
        at com.atlassian.confluence.extra.jira.JiraIssuesServlet.doGet(JiraIssuesServlet.java:98)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:42)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

      Also if you visit the url in IE, IE will throw an invalid xml error.

      If the characters are encoded as the other fields (description, summary etc), then the xml will render fine in IE and display in JiraIssues.

      The workaround if possible is to specify the encoded values for the custom field. I.e. rather than set "Dérivés" set 

      D&#233;riv&#233;s

      and this will show up in the UI as "Dérivés" but will be passed as the encoded value when the xml is built.

      Attachments

        Activity

          People

            Unassigned Unassigned
            pkamal Partha
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: