Some custom fields add themselves again to the JQL when sorting, hence breaking the JQL

XMLWordPrintable

    • 5.02
    • Severity 2 - Major
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      Some custom fields like "<input type="text" AUTOFOCUS onfocus=document.write(12*12)>" mentioned in the QA data add themselves again to the JQL when sorting.

      Steps to Reproduce:
      1. Add the custom field column like "<input type="text" AUTOFOCUS onfocus=document.write(12*12)>" to the issue navigator.
      2. Perform a JQL search like "ORDER BY <input type="text" AUTOFOCUS onfocus=document.write(12*12)> ASC"
      3. Click on the custom field header to reverse the sort.

      The Custom Field's Key "cf[12345]" gets added to the JQL and hence complains about multiple use of same custom field.

      The JQL now looks like "ORDER BY cf[12345] ASC, <input type="text" AUTOFOCUS onfocus=document.write(12*12)> ASC"

      This issue is seen only for custom field which have these Special ASCII characters in them. Not a normal custom field name like "dlkfjlkfdsflj"

            Assignee:
            Unassigned
            Reporter:
            Kiran (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: