Retain the link to the integration item in requirements
After importing work items from Azure DevOps or Jira via one of the integrations, the link to the associated work item is visible within the Testersuite . When you save the requirement to the Master List and then Test cycle it within another Test cycle , this link is no longer present. This is because a work item can only be Testersuite to a single instance in Testersuite . As a result, you did not always have a clear overview of where your requirement originally came from.
To address this, when a work item is imported from Jira/Azure DevOps, a comment line is now added to the Testersuite containing a link to the original work item. This comment line is retained when the requirement is Test cycles in different Test cycles via the Masterlist. This ensures that you Testersuite have a reference to the original work item in Testersuite .
Azure DevOps Integration Workflow Complete
Communicating changes between Testersuite Azure DevOps is the most important part of this integration. However, a key component was still missing from this workflow. When the status of a Testersuite was updated due to a change from Azure DevOps, the email rules in Testersuite were Testersuite being followed. To Testersuite the workflow between Azure DevOps and Testersuite , this has now been fixed.
When the status of a Testersuite changes due to an update in Azure DevOps, the email rules Testersuite in Testersuite are now automatically triggered. This ensures that your testers are Testersuite notified via email from Testersuite of status changes in linked Azure DevOps items.