Test Management for Jira Server

Version 4

This topic contains descriptions of new features and bug fixes for Test Management for Jira Server.

The most recent changes are listed at the top of the page.

4.9

This section contains multiple releases

4.9.3

  • Released 23 August 2018.

  • Compatible with Jira 7.X and later.

New Feature: Create Test Cycles from the Issue Screen
We added the option to create test cycles on another project from the issue screen.

Update: Improved Dates
Date formatting and date pickers have been updated and improved. The format is now standardized with Jira.

Update: Folder Structure Improvements
We made performance improvements to decrease loading time when working within folder structures.

Update: Added Redirect for Test Keys
A new functionality has been created to allow a redirect from legacy test run keys (e.g. ABC-R123) to new test cycle keys (e.g. ABC-C123).

Bug Fixes

  • We fixed a bug that caused issues when multiple fields within an Agile board were edited rapidly.

  • We fixed a bug that cleared the custom fields of a test case when importing it from another project.

  • We resolved a style issue created when multiple folders were dragged to a new position in the tree.

4.9.2

  • Released 13 August 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed a problem occurring when trying to filter reports by custom fields that contained names without whitespace.

  • We fixed a bug in the Test Player that displayed test steps in random order when using the Postgres database.

  • We fixed bug that prevented links from being displayed on the Issue page after migrating from older versions.

4.9.1

  • Released 03 August 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We resolved all issues related to printing reports.

4.9.0

  • Released 02 August 2018.

  • Compatible with Jira 7.X and later.

New Feature: Streamlined Test Execution
Enhanced test execution from the Issue screen streamlines test execution for Agile teams. You can now start a new test execution without creating a new test cycle.

Update: Test Cycles Name Change
Test runs have been renamed to test cycles. The functionality of the tool remains the same.

Update: Test Execution
Test results have been renamed to test execution. The functionality of the tool remains the same.

Bug Fixes

  • An error caused by pressing tab at the lest step of an execution has been resolved.

  • We fixed bug in the Test Cycle Tooltip, causing the data from the section "not executed" to display incorrectly.

4.8

This section contains multiple releases.

4.8.2

  • Released 04 July 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • The API has been fixed to allow for successful retrieval of test plans linked to test runs.

  • A problem was resolved to ensure users are able to avoid including unwanted test cases when creating a test run from the Issue screen.

  • We fixed a concurrency issue caused by rendering reports or using filters for test cases, plans, and runs.

4.8.1

  • Released 26 June 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed an issue causing test plans and test runs to clone incorrectly.

  • Default parameter values are no longer required to be removed for executions to made successfully.

4.8.0

  • Released 20 June 2018.

  • Compatible with Jira 7.X and later.

New Feature: Enhanced Call to Test
We enhanced Call to Test functionality (formerly Shared Steps) to boost re-usability for large scale test cases libraries. It now allows you to break down test cases into smaller, reusable pieces. Then, Call to Test recombines these test cases to achieve larger end-to-end testing scenarios. Test cases can be referenced (called) in other test cases to create nested, reusable structures. Using these, the test team can combine as many variations as needed to test the application by both functional area and end-user workflow.

New Feature: Accelerated Design with Data-Driven Test Cases
The brand new Test Data functionality unlocks Data-Driven testing (DDT) inside Adaptavist Test Management for Jira. DDT is a test design approach where test data are separated from the actual test case. DDT enables the repetition of the same sequence of test steps with the help of a data source in order to drive the input values of those steps and the expected values while verification steps are performed. Commonly, test cases are designed using variables in the test step level. A variable placeholder is added in the test step to receive the values from the data source instead of using hard-coded or fixed values.

New Feature: Modular Parameterized Test Cases
Parameterization has been introduced to allow the users to create even more generic test cases and reusable modules. In essence, parameters are used to unlock more flexibility when calling or invoking test cases. You can invoke a reusable test case by passing a set of parameters, which can affect how input or output data are displayed or processed during the test execution. Parameters can contain default values, however, the tester should be able to change each one of the default parameters according to the context of the test at hand.

Update: View Last Test Result and All Test Results
We’ve added the option to view by Last Test Result and All Test Results using the Custom Query function.

Update: REST API Attachments
Now you may retrieve or delete attachments of test cases and test results from the REST API.

Bug Fixes

  • We fixed an incorrect permission message being displayed when users were not logged in.

  • We fixed an issue caused by the wrong test case version being selected when users bulk-added test cases to a test run.

  • We fixed a spelling error in the report: Test Execution Scorecard by Project.

  • We updated test scripts to remove performance issues.

  • We fixed errors in translation to German.

  • An issue was resolved which caused the Import From Other Projects function to error.

  • An error in the Traceability Matrix was found and fixed.

  • An error was fixed which disallowed parenthesis to be used in parameters.

  • We fixed an error causing integer overflow in some reports.

4.7

This section contains multiple releases.

4.7.2

  • Released 05 June 2018.

  • Compatible with Jira 7.X and later.

Update: Improved UI
UI compatibility for Jira 7.10.0 has been improved.

4.7.1

  • Released 01 June 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed a bug that was causing problems for users upgrading from version 4.5.x directly to 4.7.0.

4.7.0

  • Released 30 May 2018.

  • Compatible with Jira 7.X and later.

New Feature: Scrum and Kanban Boards
Test Management for Jira (TM4J) integrates and enhances Scrum and Kanban boards by displaying and managing tests and traceability links directly from the issue’s Detail View. From this view you can track the coverage of test execution results and traceability links for test runs and plans.

Update: Display and Hide Traceability Links
In this new setting, you can hide Test Management for Jira sections from the Issue View page when no links exist to test cases, runs, and plans. By doing so, you can save space on the page.

Update: Improved Traceability
The brand new unified and enhanced traceability section for the Issue View page is now available. The redesigned traceability section received many performance improvements, including pagination for test cases, runs, and plans.

Update: Time and Date Formats
Test Management for Jira now uses the same time and date format configured in Jira. Jira system administrators can configure the format in the Look and Feel page. This allows you to customize the way times and dates are presented to users throughout the TM4J and Jira user interface.

Bug Fixes

  • We fixed incorrect filtering of test cases by sub-folders in Oracle.

  • We removed an error message that displayed when deleting folders with test plans inside.

  • An error preventing custom fields containing a dot character from being filtered correctly has been resolved.

  • We removed an error occurring when folders contained a forward slash.

  • We removed an issue where having A/B/B/C as the folder structure prevented tests from displaying in C.

  • We improved functionality to ensure filters are preserved when switching from one test run to another.

  • We fixed a bug preventing test cases with folder names containing "IN" from being displayed.

  • We fixed issues in the TestRail XML file importer.

  • We fixed a problem in the Detailed View, causing runs and plans not to show in the selected folder.

  • We replaced a missing style in checkboxes for grids.

  • We improved performance for handling deleted versions in Grids.

  • We improved performance for handling deleted users using Grids.

  • We improved performance for handling deleted users listed in the "created by" section.

  • Folders with quotes in the name are now allowed.

  • We eliminated an error causing Jira to fail when users tried to clone test runs.

  • We solved performance issues preventing Confluence page links from responding promptly in Jira.

  • We fixed an issue related to the Test Case Search API using bad maxResults logic.

  • A TM4J "Loading user" error is now resolved.

  • We fixed the "filter by folder with special characters" functionality.

  • We fixed the "filter by folder with comma" functionality.

  • We improved performance for handling issues without priority in the following report: Issues > Issues Reported During Testing (List).

  • We fixed an issue preventing more than one image from being added to test case results.

  • We fixed the error of double clicking 'Add' on Search Test Cases modal causing duplication.

  • We fixed a bug causing the owner of a spreadsheet to not be reflected on the related field after an import.

  • We fixed an error causing imported test cases form XML with parameters to include an extra character in all parameters.

  • We solved an issue related to deleted test cases remaining visible in the issue.

4.6

This section contains multiple releases.

4.6.5

  • Released 25 May 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • Users could not list test runs grouped by test plan, if the test plan was deleted. This issue has been resolved.

  • We fixed an issue causing no test runs to be found after changing the folder structure.

  • We fixed the functionality of filtering by user to allow fields containing dots to be included.

  • We fixed the issue of filters resetting when changing between views.

  • We resolved the issue of wrong test cases displayed when filtering by specific test case folders.

4.6.4

  • Released 07 May 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed an error causing sub-folders in specific Oracle versions to be selected incorrectly.

4.6.3

  • Released 07 May 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • Several issues in the new Grids, related to folders and custom fields containing special characters, have been fixed.

  • We fixed the issue of the selected folders and filters resetting when changing tabs in Grids.

  • Pagination was added to REST API endpoints so as to not limit page size.

  • We fixed errors occurring within REST API endpoints when project keys contained reserved words.

4.6.2

  • Released 25 April 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We resolved errors in deleting users, versions, issues, and components for Grids.

4.6.1

  • Released 23 April 2018.

  • Compatible with Jira 7.X and later.

Update: Grids Performance Improvement
Performance improvements have been made to the new Grids feature.

Bug Fixes

  • We fixed an issue in the new Grids related to having folders with special characters in their name.

4.6.0

  • Released 16 April 2018.

  • Compatible with Jira 7.X and later.

Update: New Grid View
The new Grid View gives the user a better visual experience and the flexibility to personalize display options. As a result, clicks are reduced and efficiency is increased.

When you are in Grid View, you can manage the display in the following ways:

  • Column sorting

  • Showing and hiding columns

  • Pagination

  • Moving columns by dragging and dropping

Personalized display options will only be associated to the logged in user.

New Feature: Import Test Cases from File
The "Import Test Cases from File" wizard is now available in the Test Library View for easy access to migration and importing capabilities.

New Feature: Test Management Reporting for Confluence
Leverage Test Management for Jira’s powerful reporting engine to generate reports right inside Confluence. Track coverage, progress, and quality in one central location.
Benefits include:

  • Live reports on Confluence

  • Up to 60 macros designed specifically for QA professionals

  • Powerful filtering capabilities for non-technical users

Test Management for Confluence (TM4C) requires Test Management for Jira 4.5 onwards. Learn more on the Atlassian Marketplace.

Update: REST API Support for Parameters
There is now REST API support for parameters.

Bug Fixes

  • We fixed an issue causing errors when generating the report Test Execution Results (Detailed) for test cases with 100+ steps.

  • We fixed an issue preventing proper deletion of attachments in the latest version of a test case.

  • We fixed an issue causing new test case versions to generate incorrectly.

  • We removed a bug causing icons in traceability reports not to display.

  • The report, Top 10 Defects Impacting Testing, has been improved.

  • All issues in the test case history have been resolved.

  • We fixed an issue in the REST API that prevented querying test cases using labels and names.

  • Improvements and bug fixes were made to the function "dataset export" from test execution reports.

4.5

This section contains multiple releases.

4.5.5

  • Released 16 March 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed a big causing the report, Top 10 Defects Impacting Testing, to render incorrectly.

  • A performance bug for Test Execution Results (Detailed) reports, on Oracle and the SQL server, has been removed.

  • We fixed a bug preventing the proper filtering of reports and fields containing special characters.

4.5.4

  • Released 13 March 2018.

  • Compatible with Jira 7.X and later.

Update: Improved Test Execution Results (Detailed) Report
Performance improvements have been made to the Test Execution Results (Detailed) report.

Update: REST API Improvement
The field "Support Field Owner" has been added to test runs, allowing for additional user customization.

Bug Fixes

  • We fixed a bug in the REST API causing errors when querying test cases using labels and name filters.

  • We fixed a bug causing attachments of the latest version of a test case to delete incorrectly.

  • We fixed a bug causing the error message "attachment creator not cloned" to display when cloning test cases.

  • We removed a bug from the Test Player causing custom fields from test cases from other projects not to display.

  • We fixed an error in traceability reports causing an issue’s icons to display incorrectly.

  • We fixed an error in reporting counted issues for Test Player runs.

  • We removed unnecessary SQL exceptions in Jira logs.

4.5.3

  • Released 05 March 2018.

  • Compatible with Jira 7.X and later.

This version has a data migration on the database that can take up to a minute to complete.

New Feature: Shared Test Steps
Users may now allow for shared test steps in test cases with parameters.

New Feature: Bulk Cloning Added
Test runs may now be cloned in bulk. This should save users time and effort when cloning large numbers of runs.

New Feature: Clone Test Plans
A new function has been added: the ability to clone test plans.

Update: Automatic Configuration for Traceability Links
Traceability links may now be configured automatically.

Update: Custom Fields for Test Steps
New custom fields have been added for Test Steps.

Update: Show Mandatory Field Errors
Mandatory field errors now show when trying to save a test case, plan, or run.

Update: Drag-and-Drop
Drag-and-drop performance has been improved when re-ordering multiple items at the same time on the Test Run screen.

Update: Export Dataset for Test Execution Reports
The option to "Export dataset" for test execution reports is now available.

Update: REST API: Search Test Plans
A search feature has been added to REST API.

Update: Performance Improvements
Multiple improvements have been made to increase performance and speed for work done in TM4J.

Bug Fixes

  • We fixed a bug causing reports to filter incorrectly when using Internet Explorer.

4.5.2

  • Released 13 February 2018.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed a bug causing report filters to behave incorrectly.

4.5.1

  • Released 02 February 2018.

  • Compatible with Jira 7.X and later.

New Feature: REST API Endpoint
A new REST API endpoint has been added to enable users to search for test plans.

Bug Fixes

  • We fixed a bug in the REST API to ensure that successful completion of the function, Post to /testresult, displays a code 200 instead of 201.

  • We fixed a bug causing an error when users click an impacted result in the Issue View screen.

  • The report and filter sections have received performance improvements and bug fixes.

  • We fixed a bug causing errors when pasting tables from Microsoft Word.

4.5.0

  • Released 08 January 2018.

  • Compatible with Jira 7.X and later.

New Feature: Reports
Now up to 70 out-of-the-box reports will help test managers to adequately gauge quality by tracking information about test libraries, issues reported during testing, test execution results, and traceability.

New Feature: Custom Queries
Custom Queries allows you to generate reports by building structured queries into search fields and custom fields from test cases, test runs, test plans and test execution results.

New Feature: Jira Dashboard Gadgets
Get real-time insights into your testing progress with up to 60 out-of-the-box gadgets.

New Feature: eazyBI Integration
Extend existing report capabilities by creating custom Jira reports, charts, and gadgets with easyBI.

4.4

This section contains multiple releases.

4.4.11

  • Released 22 February 2018.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We standardized the number format for all reports.

4.4.10

  • Released 14 February 2018.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We created a fixed to avoid a potential conflict with older versions of Jira Agile.

4.4.9

  • Released 09 February 2018.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We fixed a bug that caused tables to be pasted from Microsoft Word to TM4J incorrectly.

4.4.8

  • Released 04 January 2018.

  • Compatible with Jira 6.3 and later.

Update: Improved German Translation
Translation into German has been improved.

Bug Fixes

  • We fixed a bug causing an error when users selected or switched the project on IE11 and Jira 6.3.x.

4.4.7

  • Released 07 December 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We fixed a bug that was preventing successful imports from TestRail when cases contained rich text formatting.

  • We fixed a bug, preventing the successful linking of plans and runs to an Issue, on Jira 6.X.

  • We fixed a bug related to exporting test cases to XML. The attachment names were not escaped or displaying in a CDATA tag.

  • We fixed a bug causing errors when deleting custom fields.

  • We fixed a bug preventing test case filter name changes from taking immediate effect.

  • We removed a bug in the "Add Existing Test Case" screen which was causing the option to "Add Other Checkbox" not to display.

  • An error displayed when cloning test cases with long names has been removed.

4.4.6

  • Released 27 October 2017.

  • Compatible with Jira 6.3 and later.

Update: Improved Security
Security has been improved to help prevent script injection on HTML.

Update: Improved Logging for PDF Exports
The PDF Export action for test cases now has improved logging.

Bug Fixes

  • A test case dialog has been added on the Test Run screen. This enables the possibility of adding the same test case more than once.

  • We fixed a bug causing test cases to import from TestLink with incorrect label fields.

  • Test run persistence has improved the process for assigning testers in some specific scenarios.

  • Test case filters using special characters in the name may now be saved.

  • The layout of test case steps when using large words has been fixed.

  • The traceability report has been fixed so that all environments are now able to be displayed.

4.4.5

  • Released 26 September 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • Users are now able to delete test case links from Issue screen panels.

4.4.4

  • Released 25 September 2017.

  • Compatible with Jira 6.3 and later.

Update: New Public API Endpoint
A new public API endpoint has been added, to retrieve the latest test result of a test case.

Update: ID of Test Results
You may now return the ID of test results with using GET /testrun/:key.

Bug Fixes

  • We fixed erring dropdown and pop-up menus.

  • We fixed an issue causing errors when comparing versions on IE11.

  • We fixed an error causing new datasets on IE11 to generate incorrectly.

  • The Test Player now replaces special characters with values.

  • Jira service desk queues were not working when using SD version 3.8.1. This issue has been resolved.

  • We ensured the correct display of the Test Management Global menu.

  • We fixed an issue causing some charts to show numbers instead of names and values.

  • The ATM was not working properly in Jira 7.5 with SQL Server. This issue has been fixed.

4.4.3

  • Released 18 September 2017.

  • Compatible with Jira 6.3 and later.

Update: Jira 7.5 Support
Support is now available for Jira 7.5.

Update: New Parameter: Field Owner
The parameter "Field Owner" was added to the Test Plan and Test Run screens.

Update: Color Comparison
Color comparison has been added in the Compare Version screen.

update: New Custom Field: User Picker
A new custom field has been added: "User Picker".

Update: Filter by Issue Link Endpoint
A new filter, "Issue Link Endpoint", has been added in the API.

Bug Fixes

  • We eliminated an error causing the test case to duplicate when filtered by the Add Existing Test Case dialog.

  • We fixed a bug causing freezing in the Add Existing Test Case dialog on Oracle.

  • Now, {{name}} will display for all tabs in IE11.

4.4.2

  • Released 04 September 2017.

  • Compatible with Jira 6.3 and later.

Update: Pagination for Search Issues Dialog
The Search Issues dialog now has pagination.

Update: Impacted Test Results on Issue View
An Impacted Test Results section has been added to the Issue View page.

Bug Fixes

  • We fixed an error causing the Test Execution Matrix report to not display the latest test result.

  • We resolved an error related to trying to delete more than 1000 test cases at a time.

  • We fixed a counting error related to adding hundreds of test cases into a test run at once.

  • We fixed a bug that caused an error when cloning a test run with custom fields.

4.4.1

  • Released 25 August 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • The list of projects now displays when installing ATM for the first time in some databases.

  • An error preventing test cases and test runs from displaying in the Issue View page for older Jira versions and some databases has been fixed.

  • A bug causing the wrong charts and statistics to display when filtering reports by test plans with test runs from different projects was removed.

4.4

  • Released 22 August 2017.

  • Compatible with Jira 6.3 and later.

New Feature: Traceability Links for Issues
It’s now easier than ever to link test cases to Jira issues in order to establish requirements for coverage. Also, you may trace test runs and test plans to ensure that they have the most important aspects of the product covered from a testing standpoint.

New Feature: Traceability Links for Test Cases, Plans, and Runs
By using the new traceability engine, you can create a one to many relationship between test cases, issues, test runs, test plans, and Confluence pages. Also, you can trace requirements stored in external tools by using the brand new "Web links" traceability option.

Update: "Track Related Tests" Runs Automatically
Test runs related to the covered test cases are now automatically listed in the Issue View page. You no longer need to link the test run manually to ensure traceability.

New Feature: Automatic Issue Links
Issue linking allows you to create an automatic association between issues reported during the test execution and the user stories covering the test cases executed. When you file a bug during the test execution, this bug is linked to the user story covered by the test case. This behaviour is disabled by default.

Update: Track Previous Test Results
Now you can easily track previous test results right inside the Issue View page. Just click on the test case to drill down and see the latest test results.

Bug Fixes

  • We fixed a bug causing Test Importance to import incorrectly from TestLink.

  • We fixed a bug related to test descriptions importing incorrectly from Test Rail.

  • We fixed the issue of the API not displaying "application/json" in the Representation field for some REST clients.

4.3.5

  • Released 18 December 2018.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We fixed an error which caused the deletion of custom fields with empty values.

4.3.4

  • Released 26 October 2018.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We fixed the issue of text escape when exporting Test Cases to PDF.

4.3.3

  • Released 08 October 2018.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • A limit for exporting test cases to avoid memory issues during the process has been introduced. The maximum number of test cases that can be exported at once is 5,000.

4.3.2

  • Released 02 August 2017.

  • Compatible with Jira 6.3 and later.

Update: Actual Result Field
A new field, "Actual Result", displays in the test step when running a test case.

Update: Issue Status in the Test Player
The Issue Status now displays in the test steps of the Test Player screen.

Update: UI Change
A minor UI redesign in the Test Script tab of the Test Case screen has been completed for an improved experience.

Update: Select Test Case Version
In the Add Existing Test Cases screen, you can now select the test case version.

Bug Fixes

  • We fixed the Test Results (Detailed) report, which was displaying manual execution for all test cases.

  • We fixed a bug causing Test Importance to import incorrectly from TestLink.

4.3.1

  • Released 24 July 2017.

  • Compatible with Jira 6.3 and later.

Update: Export to PDF Version Number
Export to PDF now displays the version number of the test case.

Update: Confirmation Dialog for New Test Cases
A confirmation dialog now displays before creating a new version of a test case.

Update: Typing Tab for Parameters
Typing tab in the last row of the parameters table now creates a new row.

Bug Fixes

  • A counting error was fixed, related to generating the Test Case Summary report with test cases using versions.

  • We fixed a MySQL error displayed when generating a Test Case Summary report.

  • We eliminated issues related to generating correct traceability reports filtered by folder.

  • Test run filters no longer reset automatically.

  • We applied a fix for the display of disordered steps in the Compare Versions dialog box.

  • We fixed a bug causing some reports not to render on Oracle.

  • We solved an issue of some users test cases not rendering in the Issue’s coverage section on Jira versions prior to 7.0.

4.3.0

  • Released 17 July 2017.

  • Compatible with Jira 6.3 and later.

New Feature: Test Case Versioning
You can now add versions to test cases within Jira. When there are updates to the features a test needs to cover, you can now associate a version to your test case to make that clear.

You can also compare versions, see the history of changes by version, and report on multiple versions of the same test case. That means you can manage the results of testing on all versions of an application with a single test case rather than having to clone the test case for each supported version.

New Feature: Test Case Parameters
We have added the option to define Datasets and use them across test cases as parameters. You can also define parameters for each test case.

This feature enables you to define rich data sets for your testing, with multiple variations, to ensure the test coverage is achieved without the need for duplicating test cases.

New Feature: Test Results (Detailed) Report
We have added a new report, Test Results (Detailed), which reports the test step results level. This will help teams who work in regulated environments and need to report to this level of granularity.

Update: REST API Improvements
Now, it is possible to search test runs from different projects. Use the following REST API functions:

  • GET /testrun/{testRunKey}/testresults

  • POST /testrun/{testRunKey}/testresult

Bug Fixes

  • We updated our Send us Feedback links in the application to direct users to the Service Desk for an improved support process.

  • The Default Steps View mode is now "GRID" by default, as opposed to "LIST".

4.2

This section contains multiple releases.

4.2.4

  • Released 30 June 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • TestRail’s functionality is now restored.

4.2.3

  • Released 29 June 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We fixed the issue of custom test case statuses rendering incorrectly.

  • We fixed issues of access to the project configuration panel.

  • We remedied an error in which deleted test runs had unintended clones.

4.2.1

  • Released 07 June 2017.

  • Compatible with Jira 6.3 and later.

Update: Global Project Administration
We have added a Global View to allow users to see which of their projects have Adaptavist Test Management enabled or disabled.

Update: Global Access Restrictions
Global access restrictions allow you to define which user can access test management. By default, access is enabled for everybody. However, you can restrict access only for users in specific groups and roles.

Update: Manage Projects Restrictions
In the Test Coverage section of a Jira issue, you can view a column with the latest test result for each test that covers this issue. You can also view this information on all grids displaying test cases.

Bug Fixes

  • We updated the new Test Player UI to improve rendering in Safari, Internet Explorer, Edge, and Chrome.

  • The Test Case key is now included when exporting to Excel.

4.2.0

  • Released 22 May 2017.

  • Compatible with Jira 6.3 and later.

New Feature: Edit Test Runs in Bulk
Test run creators and editors can now update the details of test runs in bulk, saving time and duplicated effort.

New Feature: Clone Test Runs with Linked Issues
We have added a new option to the Test Run Clone to enable linked Jira issues to be cloned across with the test run.

Update: Streamlined Usability of the Test Player
We have improved the way users will interact with the test steps in the Test Player. We have surfaced the most common step results via icons so results can be recorded in one click rather than the previous menu options.

Update: Updated "Send us Feedback" Link
Following the migration of the Kanoah Service Desk to Adaptavist Product Support we have updated the destination of this link in versions 4.2 onwards of Adaptavist Test Management.

Update: REST API Improvements
Now, when retrieving test runs, the status and execution date information is included.
Also, there is a new field for test runs: Execution summary. This field summarizes the statuses of all its items.

Support has been added for creating and modifying issue links of Test Results via the API.

Bug Fixes

  • We fixed the issue of not being able to copy and paste screenshots in the WYSIWYG editor.

4.1

This section contains multiple releases.

4.1.3

  • Released 11 May 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We fixed an issue on API endpoint: the command /testrun/search was unsuccessful when used in the Oracle database.

4.1.2

  • Released 05 May 2017.

  • Compatible with Jira 6.3 and later.

Update: New API Endpoint
A new API endpoint for creating folders has been added.

4.1.1

  • Released 28 April 2017.

  • Compatible with Jira 6.3 and later.

Bug Fixes

  • We resolved the issue that caused an error on a data migration of version 4.1.0.

4.1.0

  • Released 27 April 2017.

  • Compatible with Jira 6.3 and later.

New Feature: Shared Test Steps
One of our most requested features is here.

Create centralized test libraries to re-use across your test case repository. Now users may update changes in one place and select to propagate across all test cases using the test steps.

Learn more by reading Managing and Reusing Test Cases.

This is the first release of this feature so we would love any feedback.

New Feature: Comments for Test Cases, Runs, and Plans
There are now new tabs in the Create and Edit mode which allow for comments on test cases, runs, and plans.

This feature enables your QA teams to collaborate on the creation and maintenance of your Test Artefacts.

Update: New REST API Endpoint: PUT /testcase/{testCaseKey}
Test case now supports the PUT command to enhance the options for integrating with your automated testing.

Bug Fixes

  • We fixed a bug causing test steps to display in reverse order when exporting test cases to Microsoft Excel.

  • We fixed an error causing the wrong "created on" and "update on" timestamps to display on PDF exports.

  • We fixed a bug causing test cases to display in the wrong order when executing a test run.

  • Resolved API Issues:

    • Users were unable to create test cases with folders having the same name of test run folders.

    • Users were not able to create a test case with zero steps.

    • The test run search did not filter by folder when a folder name contained special characters.

    • Dashes in labels were converted to underscores when creating a test case.

4.0

  • Released 20 April 2017.

  • Compatible with Jira 6.3 and later.

Update: New App Name
In the application, the Project Settings pages and all other references to Kanoah Tests are now updated to Adaptavist Test Management for Jira.