Applies to TM4J Server/Data Center 7.1, last modified on August 12, 2020

This topic contains descriptions of new features and bug fixes for TM4J Server/Data Center. 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 TM4J version that is compatible with your Jira. Version 7.0.x-jira7 is compatible with Jira 7 only, and version 7.0.x is compatible with Jira 8.x and later.

7.1.0

  • Released on August 12, 2020.

  • Compatible with Jira 7.X and later.

Custom fields API

This release includes the addition of custom field endpoints to the TM4J Server API. Using the new endpoints, you can now enable TM4J and create custom fields for one or many projects.

We’ve added this to the API to make it quicker for teams to configure multiple Jira projects with the same custom fields.

You can find the API documentation with more information here:

https://support.smartbear.com/tm4j-server/api-docs/v1/

Other improvements

  • We changed the API for test executions to set the assignedBy field to unassigned by default if no username is set.

  • We changed the Test Execution reports to make them more readable with large number of data elements.

Bug fixes

  • We fixed a bug where the attachments of test case steps were removed when attachments were deleted from another version of that test case.

  • We fixed a bug where users were unable to see the timer button to start the execution with normal zoom in the test player.

  • We fixed a bug where the API updates to custom fields used deleted custom field names.

  • We fixed an issue where the drag and drop for test steps inside test script wasn’t working.

7.0.3

  • Released on July 7, 2020.

  • Compatible with Jira 7.X and later.

Improvements

  • We have improved the test cycle grid performance for test cycles with many previous test executions.

  • We have improved the performance in the test player for test cycles with many previous executions.

Bug fixes

  • We fixed an issue preventing labels from being deleted on test cases imported from other Jira projects.

  • We fixed an issue where two entries are created in the change history for custom field value changes.

7.0.2

  • Released on June 17, 2020.

  • Compatible with Jira 7.X and later.

Bug fixes

  • We fixed an issue preventing test case imports when a folder has an empty name.

  • We fixed an issue with the “Add test cases” pop-up loading all test cases for a given project, rather than the first page.

  • We fixed an issue with the test cycle grid, where cycles were hidden when one of the cycles had an invalid user assigned.

7.0.1

  • Released on April 15, 2020.

  • Compatible with Jira 7.X and later.

Bug fixes

  • We fixed an issue where deleted custom field values appeared when editing a test case

  • We fixed an issue with gadgets, where the text was incorrectly formatted when displayed

  • We fixed an issue with the traceability reports showing "No epic" or "No coverage" labels incorrectly.

  • We fixed an issue where the test cycle progress bar was missing in the grid.

  • We fixed the missing "Last test execution" result display to show test cycle state.

  • We fixed the UI issue for notifications so that they're no longer cut off.

7.0

  • Released on March 31, 2020.

  • Compatible with Jira 7.X and later.

TM4J joins SmartBear
We are excited to announce that TM4J is joining the SmartBear family! Read more in the announcement.

Find test cases without a folder
A new filter option called None is available for the Folder filter, making it easier to locate test cases that are not organised within folders.

Improved performance
We improved TM4J’s browser loading time in the 6.9.1 release, and now we’ve optimised browser performance even more!

Bug fixes

  • We fixed an issue that would not allow users to save a test cycle if it included a test case associated with a deleted user.

  • We fixed a UI issue that affected the way comment-prompt text appeared for test cases, cycles, and plans.

  • We fixed an issue with the REST API that prevented the ability to download automated test cases for specific projects.

See Also

TM4J Server/Data Center Release Notes

Highlight search results