defect trigger when status changes for products & requirements
We are always working on streamlining workflows in Testersuite. For example, it is not always necessary to test based on test cases in a test run. You can also choose to test directly at the level of products and requirements and indicate the test result in the form of a status change.
To better support this, from this release onwards, it is possible to defect the creation of a defect when a product or requirement is assigned a specific status. This can be configured in the customizing settings in the "Status" field for products and requirements:
When a product or requirement is given the statusdefect ," the user will immediately be asked defect a defect in a pop-up screen. This works in the same way as when a step in a test run is given the status "Not OK":
Link to Testersuite after retrieving Azure DevOps work items
When writing defects Azure DevOps via the Azure DevOps integration, a link to the original Testersuite is placed in the newly created Azure DevOps work item. This allows the item to be traced in both directions.
Starting with this release, this also applies to the other side of the integration: when you Testersuite Azure DevOps work items into Testersuite as requirements, a link to the corresponding requirement in Testersuite is now placed in the Azure DevOps item. This completes the traceability of items within the integration.
Optimization of Jira integration
Improvements have also been made to our Jira integration. By now using the Jira API in certain places instead of fixed data, the integration has become more reliable and robust. This also means that the Testersuite will continue to work when the Jira side is temporarily unavailable. This results in a more stable Jira integration for our customers, both for integration via Jira cloud and via Jira data center.