Test Management for Jira Server

Version 6

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.

If manually downloading the archive from the Atlassian Marketplace, please make sure to download the one compatible with your Jira. Version 6.1.0-jira7 is compatible with Jira 7 only and version 6.1.0 is compatible with Jira 8.x and later.

6.9

  • Released 20 January 2020.

  • Compatible with Jira 7.X and later.

This version is compatible with Jira 8.7 and includes changes for GDPR compliance. Remember to upgrade to this version before upgrading your Jira instance to ensure everything works as expected.

New Feature: Improved Import/Export Thresholds
We improved export and reporting thresholds to give you more control over your system’s performance. We made the UI language and system messages more clear, too.

Check out Setting Thresholds to Improve Performance to learn more.

Update: Support for Jira
TM4J has been updated to support the latest version of Jira.

New Import Options
You now have the ability to import a CSV or Excel file containing custom field information for test steps.

Bug Fixes

  • We fixed a bug that caused the Test Execution Results (Detailed) report not to open if it included 2100+ test executions or test cases was removed.

  • We fixed a bug causing the mishandling of test executions without a status on the GET /testrun endpoint.

6.8

  • Released 05 December 2019.

  • Compatible with Jira 7.X and later.

New Feature: TM4J Events for ScriptRunner for Jira
If you’re an avid ScriptRunner for Jira user, you might notice the addition of three TM4J events:

  • TestExecutionChangedEvent

  • TestCaseChangedEvent

  • TestCycleChangedEvent

By integrating ScriptRunner with TM4J, you can automate and customise TM4J even more to better suit your specific needs and make your testing efforts more accurate and efficient.

Example scripts are available on the Adaptavist Library.

Check out our customer documentation for the ScriptRunner for Jira integration to learn more. There, you’ll learn to create listeners in ScriptRunner using TM4J events and create script fields with ScriptRunner for TM4J data.

New Feature: Set Export Thresholds
Admins can now set thresholds (limits) for specific operations to avoid performance issues. Thresholds are available for both test-case and test-execution exports, and you can limit the number of results generated by the Test Executions (Detailed) report.

Bug Fixes

  • We fixed a bug that caused a 404 error after traceability was added to an issue.

  • We fixed a performance issue related to TestRail imports.

  • We resolved an issue in the Test Player that caused test-case environments to be unnecessarily hidden.

  • A fix has been applied for a paging issue in the Traceability Tree (Custom Hierarchy) report.

  • We fixed an issue that prevented test cycle sections from being collapsed.

6.7

This section contains multiple releases.

6.7.5

  • Released 22 October 2019.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We removed an issue that prevented test cycles with 1000+ test cases from being deleted.

  • We fixed issues arising from linked custom field values for downloading test case attachments and deleting test cases.

  • The data input for the Planned Start Date field and the time shown when exporting this data were mismatched. This bug, relatee to timezone, has been fixed.

  • We fixed an issue which caused export failures on Oracle and SQL Server for the Test Execution Results (List) report if there were many items in the list.

  • We resolved an export issue related to the Test Execution Results (List) report that occurred when a field contained more than 32 KB of content.

  • We fixed an issue that was hiding drop-down options clicked near the bottom of the screen.

  • We fixed an issue that caused the REST API endpoint /rest/atm/1.0/testcase/search to not work if any invalid test data existed.

6.7.4

  • Released 30 September 2019.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • We fixed a security issue to prevent XSS attacks from occurring in the history log.

6.7.3

  • Released 13 September.

  • Compatible with Jira 7.X and later.

Update: Support for Jira
TM4J has been updated to support the latest version of Jira.

Bug Fixes

  • We added pagination to the information displayed when viewing test executions in the Test Player, improving performance.

  • A fix was created for a malfunction with the Favourite Filters option in coverage reports.

  • To avoid performance impact, the maximum number of test cases that can be exported to PDF at one time is now 5,000.

  • Improvements were made to memory management when exporting test cases and test executions via XML and Microsoft Excel.

  • The 65.535 row limit in Excel for test case and test execution exports has been removed.

  • We fixed the non-functioning Estimated Time field in the history section for test cases.

  • An issue was fixed related to test execution progress in test cycle lists, when filtering by last test results.

6.7.2

  • Released 20 August 2019.

  • Compatible with Jira 7.X and later.

Update: Security Vulnerability Notice
This version of TM4J Test Management for Jira Server and Data Center addresses a critical security vulnerability that was recently identified in TM4J. The vulnerability affects all versions of TM4J prior to 6.7.2.

The vulnerability means that files and network resources (such as http) were accessible to the Jira server via an XML external entity (XXE) flaw. In order to exploit this flaw users must be logged into Jira and have permissions to view a project that has TM4J enabled.

If you have any questions, please feel free to raise a support request referencing JQA-7984.

6.7.1

  • Released 20 August 2019.

  • Compatible with Jira 7.X and later.

This version has been withdrawn from the Atlassian Marketplace due to an issue with a database upgrade task introduced on version 6.6.0. All changes and improvements listed below are included in the next publicly available version (6.7.2).

Bug Fixes

  • We improved performance of the export-to-Excel feature for test cases. We also changed the export format from Excel 2003 (xls) to Excel 2007 (xlsx).

6.7.0

  • Released 19 August 2019.

  • Compatible with Jira X.X and later.

This version has been withdrawn from the Atlassian Marketplace due to an issue with a database upgrade task introduced on version 6.6.0. All changes and improvements listed below are included in the next publicly available version (6.7.2).

New Feature: Archive and Unarchive Test Cases
You can now archive and unarchive test cases in the test library. This gives you the freedom to remove unwanted test cases from the test library without permanently deleting the data.

Simply select the desired test case and click Archive. All archived test cases are visible in the Archived section at the bottom of the left-hand sidebar, where the folders are located.

You can unarchive these test cases at any time by selecting, then clicking Unarchive.

To archive:

archive

To view archived tests:

view-archived-tests

To unarchive test cases:

unarchive

Update: Support for Jira
TM4J has been updated to support the latest version of Jira.

Bug Fixes

  • We fixed the issue of archived environments showing in the dropdown options for test cases in test cycles.

  • We removed a bug causing the Assigned To and Executed By fields to not be visible in the Test Execution Results (Detailed) report.

  • A bug was fixed that was preventing the Test Cycle view to load in older versions of Chrome, Firefox, and EDGE.

  • The number of auto-complete options for test cases, cycles, and plans when filtering reports has been increased.

  • The function GET /testrun/{testRunId} endpoint to block calls with empty "fields" queryParam has been improved.

6.6

  • Released 08 August 2019.

  • Compatible with Jira 7.X and later.

This version has been withdrawn from the Atlassian Marketplace due to an issue with a database upgrade task. All changes and improvements listed below are included in the next publicly available version (6.7.2).

New Feature: Test Player Screen Functionality
Now, you can delete test executions by clicking the delete icon in the Test Player.

test-screen-1

You can delete test executions by clicking the Delete icon, but use caution, as deletion is permanent and deleted test data cannot be retrieved.

test-screen-2

If you can’t delete test executions, you may need to adjust permissions in the Test Executions category.

test-screen-3

Bug Fixes

  • A bug preventing filtering test cases by custom field in the REST API has been removed.

  • A bug preventing the accurate cloning of test cases was removed.

  • We fixed a bug causing issues when trying to open the Test Cycle view.

  • Fixed a bug causing Incorrect URL in Test Execution Results by Test Cycle gadget.

  • Fixed a bug that caused the Test Execution Results by Test Cycle gadget to display an incorrect URL.

  • A bug causing failures to load in the Test Cycle view deleted test cases from Jira projects has been removed.

  • We made UI improvements in the settings section of the reporting filter.

6.5

This section contains multiple releases.

6.5.2

  • Released 11 July 2019.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • All issues related to unsuccessful imports from Test Rail have been resolved.

6.5.0

  • Released 25 June 2019.

  • Compatible with Jira 7.X and later.

Update: Support for Jira
TM4J has been updated to support the latest version of Jira.

Update: Percentage and Count Data Options
Options have been added to allow users to display data as a percentage or count in reports and charts.

Update: New Filters in Traceability Tree
An option to filter issues by coverage has been added to the Traceability Tree report.

Update: Report Display Update
Now reports display the name of test cases, plans, and test cycles in addition to the test key.

Bug Fixes

  • We fixed an error in importing custom fields for test cases from XML/CSV files.

  • We resolved an issue related to updating custom fields via the REST API.

  • A bug has been removed from scorecard reports. The issue arose when test plans contained test cases with test execution statuses of the same name, imported from different Jira projects.

  • We also fixed a bug preventing generation of the following reports:

    • Test execution matrix by test cycle

    • Test execution matrix by environment

    • Test execution matrix over time

6.4

  • Released 21 May 2019.

  • Compatible with Jira 7.X and later.

New Feature: Custom Fields for Folders
Whether you have 15 folders or 150 folders, additional information beyond folder names can provide more context for important pieces of your project.

custom-folder-field

Update: Reorder Parameters
It’s now possible to reorder parameters in the Test Script tab. This allows users to customise their view and see the fields most relevant to their needs.

Bug Fixes

  • We fixed a bug to prevent issues when executing failed upgrade tasks for the second time.

  • We also fixed a bug which was allowing users to change the description of system default statuses unnecessarily.

6.3

This section contains multiple releases.

6.3.2

  • Released 01 May 2019.

  • Compatible with Jira 7.X and later.

Update: Improved Analytics Tracking
We added improved analytics tracking, allowing you to more easily and accurately gather data.

6.3.1

  • Released 01 May 2019.

  • Compatible with Jira 7.X and later.

Bug Fixes

  • A bug was fixed which did not allow user keys to contain a space character when displaying test cases, cycles, and plans.

6.3.0

  • Released 30 April 2019.

  • Compatible with Jira 7.X and later.

New Feature: Traceability Tree Report with Custom Hierarchy
The new Traceability Tree (Custom Hierarchy) report offers you dynamic, broad-ranging traceability and test case coverage statistics. Regardless of which development items your team uses—epic, feature, story, task, etc.—and regardless of the hierarchy your team uses to structure and organize the work, the Traceability Tree report allows you a powerful high-level overview of all testing coverage.

traceability1

traceability2

Bug Fixes

  • Support for analytics tracking has been added.

  • There is now an increased number of results in the filter by folder dropdown.

6.2

  • Released 08 April 2019.

  • Compatible with Jira 7.X and later.

New Feature: Support for Bamboo
Test Management for Jira’s Bamboo integration enables you to automate tests outside Jira, run them in Bamboo during the CI/CD pipeline, and have results sent back to TM4J for reporting and tracking.

support-for-bamboo

New Feature: Improved Onboarding
The onboarding process is a critical step in having new users getting up to speed quickly. In order to provide insights and guidance, we have improved the empty state pages as part of a cohesive onboarding experience throughout TM4J. The empty state pages will provide links related to the task to be done to educate and engage new users.

onboarding

Update: Reports Filtered by Tester
In any test execution report by tester, you can now filter the results by either the tester assigned to the test case or the tester who executed the test case.

filter-by-tester

Bug Fixes

  • Pagination was integrated for the add-test-cycle dialog.

  • A bug in the test case grid causing an error when sorting the grid by custom field has been removed.

  • A bug was fixed which prevented generating report test execution results by tester.

  • We removed bug on the REST API related to errors when adding test cases to the test cycle.

6.1

  • Released 11 March 2019.

  • Compatible with Jira 7.X and later.

Update: Titles for Gadgets
Titles may now be given to identify specific gadgets in the Jira dashboard.

jira-dashbaord

name-gadgets

Update: Custom Priorities
Now custom priorities may be created for test cases. Also, priorities can be modified in existing cases using the Configuration page.

custom-priorities

Bug Fixes

  • A bug related to displaying heat maps in the gadgets and reports section was removed.

  • Layout issues for scorecard reports have been resolved.

  • A bug was fixed that caused an error in the second page of the grid view, when searching test cycles and test plans.

  • A bug was removed that caused an exporting error in Microsoft Excel files with more than 32,767 characters in a cell.

  • The REST API now allows for custom fields for test executions.

6.0

  • Released 25 February 2019.

  • Compatible with Jira 8.X and later.

Update: Support for Jira 8
TM4J has been updated in order to support Jira 8.