Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2311

[JIRAALIGN-2311] Test Case - Story Search Times Out


    • 1
    • Severity 3 - Minor
    • Avengers - USH6

      Issue Summary

      A user wants to move a Test Case to a different Story with an ID of 551130. However when attempting to search by typing in the first few digits (i.e. 551) , the search runs continuously with no results. If, however, you type in the full 551130 for the Story ID, the Story will appear and then disappear right away and can't be selected.

      Steps to Reproduce

      Log in and navigate to the "Test Cases" Page
      Click on a Test Case to bring up its slide out window
      Make sure the "Tied to:" field is set to Story
      In the "Find Story" field, start typing in the first few digits of the desired story id.

      Expected Results

      The search should return a story or list of stories to choose from.

      Actual Results

      The search churns but never returns any stories.

      The below timeout is seen in Splunk:

      2020-11-17 02:36:15 GET /AjaxFiles/Error er=98767 443 4089 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/86.0.4240.198+Safari/537.36 https://xxx.jiraalign.com/StoryGrid?Programs=413&StoryID=527891 302 0 0 47
      8:36:15.521 PM	
      { [-]
         ASP_function: OOFunctionsSql.SetRSParamsCursor
         correlationid: IbV2LnxTiK+cYB524+amGODbAgxx6h63VvFZzCYrBAE=
         customer_db: XXX
         error_description: Query timeout expired
         error_id: 98767
         error_number: -2147217871
         error_source: Microsoft SQL Server Native Client 11.0
         log_type: exception
         logfrom_location: Website-ASP
         sql: EXEC RPM_GET_STORY_LIST ?,?,?,?,?,?,?,?,?,?,?,?,?
         timestamp: 2020-11-16T21:36:15.521000-05:00
         url: https://xxxx.jiraalign.com:443/AjaxFiles/AjaxSearchStories.asp?Type=1&ProductId=413&q=55&limit=25&timestamp=1605580545264
         urlverb: GET
         user: 4089


      Currently there is no known workaround for this behavior. A workaround will be added here when available

            idziadyk@atlassian.com Iryna Dziadyk (Inactive)
            kbaxley Kent Baxley
            0 Vote for this issue
            5 Start watching this issue