Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-67974

JQL input missing from saved filter

    XMLWordPrintable

    Details

    • Introduced in Version:
      7.12
    • Support reference count:
      36
    • Symptom Severity:
      Severity 2 - Major
    • Occurrence Factor:
      75%
    • UIS:
      1,226
    • Current Status:
      Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center

      Description

      Summary

      JQL search panel is missing when viewing custom filter.

      Symptoms

      <Jira>/rest/api/2/filter/favourite?expand=subscriptions[-5:] endpoint responds with http code 400

      Steps to reproduce

      1. Install Jira 7.12.2
      2. Create sample project
      3. Save filter with any JQL
      4. Go to saved filter

      Expected result

      Page shows JQL on top of the issue list and issue view

      Actual result

      JQL panel is missing.

      Workaround

      1. Open configuration file server.xml (should be in conf directory)
      2. Find all connectors your application is using
      3. Add relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" to properties for example: 
        <Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>
      4. Restart Jira
        See KB for full details: changing server.xml to handle requests with special characters

      If you have multiple connectors in Jira, add the new parameters to each connector.

      Notes

      Cause of the issue is new version of Tomcat (8.5.32) which was updated in 7.12.2.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                psuwala Piotr Suwala
                Reporter:
                pczuj Przemyslaw Czuj
              • Votes:
                22 Vote for this issue
                Watchers:
                86 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: