8.9.4 Release Notes - Feb 06, 2018

13186 - Unable to link a Jira story to a Test Run
14168 - Unable to switch between pages when quickly clicking on objects such as Requirements, Test Cases and Test Runs on the tree
14171 - It shows incorrect linked Requirements of a Test Case
14174 - Unable to download attachments from TestPad
14325 - When copying and pasting a Test Cycle to create a new copy of the same, custom field values of the Test Suites under the Test Cycle are not getting pasted
14302 - Test Runs are added with the wrong order
13356 - 2 scrollbars in Data Query pages
- The scrollbar which were applied to the whole page is removed
- You can collapse the Query section to have more space to view the query result grid

8.9.3 Release Notes - Feb 02, 2018

11404 - Unable to use hot-keys to copy text from read-only fields
13715 - API search artifact - Page size parameter is not working
13787 - Self links to Test Runs are missing in the response of Get multiple Test Runs API
13811 - Unable to insert line break in Notes section of Execution Log when submitting Test Logs using API POST /api/v3/projects/ProjectID/auto-test-logs?type=automation
13912 - Unable to retrieve the test run via the SDK

When organizing imported Requirements from Jira by "Parent" field, the folder is named as "ID +Summary of the parent issue."
When searching for Requirements to add them to a Jira Release scope, Jira Requirements are included in the search result but you are not able to add them to the scope of these Releases.
You are not able to remove Jira Requirements from the scope of Jira Releases.

Ability to type ahead and search for agents by names when scheduling Test Run execution
Reduce the loading time of Test Run data query when there are a huge number of Test Runs included in the query result
parentId (ID of the module) of the Requirements are added to the response of following API calls:
- GET /api/v3/projects/{projectId}/requirements
- GET /api/v3/projects/{projectId}/requirements/{requirementId}