Spell checking implemented using Google's spell checker library.

The Execution History tab in the Test Case details page provides a list of executions for the Test Case and includes all the important details of the Test Run including which Test Suite and Platform it was run on, who executed it and when, and of course the execution status. If there are any bugs associated with a Test Run they will be listed with a link to the bug details.

"In the QMetry Enterprise edition a new "Tester" column has been added that allows our enterprise customers assign different testers to specific Test Cases within a Test Suite. This is to allow companies with large Test Suites (e.g. regression suites) to divide up the work without having to create numerous independent Test Suites. Testers can be assigned one at a time or in batches with the multi-select checkbox.

QMetry organizes Requirements and Test Cases into folders at the project level. Since many Releases and Cycles only have a subset of Requirements and Test Cases some of the folders are empty. QMetry now allows users to hide empty folders to make navigating the tree easier. Note: you can unhide empty folders if you want to add new Requirements or Test Cases into one of your empty folders.

QMetry provides you the flexibility to track test results against a drop (a.k.a. build, iteration, patch, etc.) through QMetry's unique "drop" feature. At the time of execution the tester can assign a specific drop to be tested against. Now organizations can control who can set the default drop for a test cycle.

QMetry provides you the flexibility to track test results against a drop (a.k.a. build, iteration, patch, etc.) through QMetry's unique "drop" feature. Now you can set the drop using the API which can be very helpful when integrating with CI tools.

QMetry provides you the flexibility to track test results against a drop (a.k.a. build, iteration, patch, etc.) through QMetry's unique "drop" feature. Now you can set the default drop for users allowing you to test in parallel multiple drops either for testing branched code, or for hardware teams testing different firmware or configurations of platforms.

QMetry allows users to test against different versions of a Test Case. When updating a Test Case users have always been able to let past Cycles and/or Releases keep the older version of the Test Case associated with them (e.g. don't update Test Case in all builds). Now users will be able to select a default version for both older and new Releases and Cycles. This is designed primarily to help companies that need to test updates to hardware or software versions that have different functional Requirements that change Test Cases over time.

Test Case versions can be named and a comment can be added to help track versions. This helps those customers that need to test against multiple versions of a Test Case. Customers can tag each version of a Test Case and display it in the drop-down list to identify correct versions to test.

Added the ability to export UDFs and platforms.

This feature has been implemented to archive drops added by mistake or that are no longer needed.

This allows users to quickly create a Test Case directly from a Requirement copying the common fields from the Requirement to the Test Case. This is most useful when creating a Test Case that validates a bug fix or new feature when the Requirement has relevant steps to reproduce or use cases.

The Task module now has the ability to filter columns by the headers like our Requirements, Test Cases, and Test Suites modules.

When viewing the Platform list in the Admin module users can now see if a platform has any attributes and how many attributes it has.

Users can now retain the reports on their Dashboard regardless of cookies. This way users will not have to repopulate their Dashboard with the desired reports when the cookie expires.

QMetry now supports JIRA 5.0 and Activity Streams and Remote Linking technology which allows JIRA users to link QMetry Requirements and Test Cases with JIRA issues, review their status, and trace the activities thereof in JIRA.

UDF values can now be copied while adding entities from one project to another. UDF Names and Type should be the same in the source project and target project to get the UDF values copied.

An Execution Button has been added to the Test Case module to allow users to quickly test individual Test Cases, folders, or selected groups of Test Cases. This was previously only available via a right-click option in the Test Case tree. This functionality is more beneficial to those QA groups that are looking to do quick ad hoc, exploratory, or individual bug fix testing outside the normal Test Suite planning.

Editing and deleting customized lists now work properly.

This provides an alternative UI that shows the Project/Release/Cycles in a tree view similar to scope edit. The UI improves the ability to see all projects together and allows users to sort by Target and Creation date. This UI would limit the projects listed to those that the user has rights too.

Each column in the Execution History grid can now be sorted and/or filtered.

The Test Run feature allows you to track individual runs of a Test Suite against a given platform. With Test Runs companies can track and compare repeated tests against a platform. This feature is designed primarily for user acceptance testing, and for performance-based testing.

Implemented to help support JIRA's use of Remote Issue linking and Activity Streams using the REST API.

QMetry now supports integration with Rally Community and Enterprise Editions.

Improved support for special characters in QMetry. Now user can create or import a Test Case that has a summary or a description in UTF characters. This includes support for other languages like Spanish, Finnish etc. We have also added support for all UTF-8 letters in user name.

Improved search and importing of large numbers of LDAP users.

The UI now allows you to review all previously reported bugs related to a Test Case before submitting a new bug. This helps QA groups find bugs that might be related to other platforms or previous versions of the product and avoids creating duplicate issues.

The Admin module has been reorganized with a new more user friendly UI, accompanied with a guide to help existing users map the old UI with the new one. Some small performance improvements have also been added.

Added drops to the setup wizard with added ability to assign a drop to a user role and to a specific Cycle. It allows QA managers to assign various testing groups different builds, patches, firmware, etc. to test against which can help in organizing testing in an agile environment, particularly when testing parallel, or branched code is needed.

When cloning a Project or Release the backlogged items will now also get copied along with the assets of the selected Release and Cycle.

All rich text boxes are now resizable by dragging the lower right corner.

"In Test Case module, changed the grid column name from "Coverage Status" (showing value as Covered or Uncovered depending on the Requirement linked) to "Linked Requirement(s)" allowing users to see a count of Requirements covered (similar to defect count).

"While the grid view only shows the number of linked Requirements (or Test Cases) to avoid delays in rendering, QMetry has enabled the names and ID's for export to CSV. The CSV file puts the names and ID's into the "Linked Requirement(s)" or "Linked Test Case(s)" cell (e.g. If a Test Case had 3 Requirements then the "Linked Requirement(s)" cell for that Test Case row would have 3 Requirements listed - separated by line breaks)".

Test Cases and Requirements have always been linked to projects; however, when creating new Test Cases and Requirements they were previously forced to be associated with a Release and Cycle (Sprint). Now Test Cases and Requirements can be placed directly in the Backlog by associating them with the project only, or with a Release, but not a Cycle. This allows users to plan ahead and create Test Cases and Requirements in the project before a Cycle has been identified.

Performance of expanding the Tree View has been improved using AJAX.

When QMetry exports to a CSV file, the column names are now the same that are used in importing using the 'Auto Map' feature.

Additional colors have been added to the palette to make it easier to identify the different values.

The objective field is now resizable.

The reports provide the following information: 1. A summary of Test Suites showing the number of Test Runs organized by status for each Test Suite, and the total number of Test Runs for each Test Suite.
2. A long form Test Suite report showing all Test Runs organized by Test Suite.