Release v4.41.0
Dear Testify Key-User,
we proudly announce our Testify Release Updates v4.41.0 with new improvements for a better Testify experience:
Feature | Short Description | Link to detailed Feature Description |
---|---|---|
Feature extension: Text search in checklists | In checklists, there is now a search field at the top right to search for specific checks, sections or pages. This is especially useful for hierarchically structured checklists. | |
Feature extension: Include notification email in user import / export | In the manual user import there is now an additional column to add an alternative notification e-mail address. | |
Feature extension: Update user with excel import | When importing users, existing user data can now also be updated. | |
Feature extension: Add TO and TOT restrictions at group excel import/export | When exporting/importing groups, it is now possible to add test object (type) restrictions. | |
Feature extension: Handle skip or replace of null values in excel import/export | When updating data in Testify through an Excel import, there have been some adjustments. This way it can be ensured that only those cells are updated for which there is also new data:
| |
Feature extension: Preselected tab in Task View depending on existing tasks | If the "Overdue" tab in the custom tasks is empty, the tasks under "Current" are automatically displayed. | |
Feature extension: Display comments in checklist history of PDF protocols | From now on, comments are displayed with the new checklist PDF protocols. | |
Feature extension: Multi-language Export/Import of checklist templates | Checklist templates can now be imported as json-file via the context menu at "Manage checklists". | |
Feature extension: Navigate from issue to checklist overview | When opening a linked checklist within an issue , there is now an option to decide if you want to go back to the issue or the checklist. Back button: Return to the issue Exit button: Navigate to the checklist |
The following bugs were fixed:
Bug | Short Description |
---|---|
Custom fields don't get shown on V2 Issue protocol | If there are too many custom fields (more than one page in the pdf file), a white page was displayed in the output pdf file instead of the custom fields. |