Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-3003

dateCompare can produce an HTTP 400 (Bad Request) with error jqlTooComplex

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Done
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.45
    • Component/s: JQL Functions
    • Labels:
      None
    • Sprint:
      Sprint 43, Sprint 44
    • Critical Points:
      0.7

      Description

      Queries using dateCompare can return no issues, even when they ought to.

      For example, the following query of the ScriptRunner for Jira project:

      issueFunction in dateCompare("project = SRJIRA", "resolutionDate > Change completion date")
      

      Looking at the browser's Network tools, you can see that there's an HTTP 400 error being returned by <jira base URL>/secure/QueryComponent!Jql.jspa .

      While the error message itself seems to be a red herring (see JRASERVER-63507), we should investigate whether there are changes we could make to dateCompare itself to prevent this problem from showing up in the first place.

      Potential Workarounds

      Some customers have been able to work around this problem by adding a subquery to their call to dateCompare. That said, the subquery, even a fairly specific one, will not always rectify the issue.

        Attachments

          Activity

            People

            Assignee:
            rholban Roland Holban [X] (Inactive)
            Reporter:
            jcarter Jonny Carter
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: