The behaviour you are observing is correct and aligns with its design, which includes two types of direct links and one indirect type:
1. Test Case link for Issue Tracker task: These links show how tasks in the issue tracker are covered by test cases, indicating test coverage. This type helps illustrate how well various tasks are covered by tests within Allure TestOps.
2. Launch link for Issue Tracker: These references demonstrate the alignment between significant events or milestones in the issue tracker and the ones in our Allure TestOps – launches. For instance, if there’s a release task in the issue tracker, a corresponding launch reference in our system will highlight the connection between this milestone and related activities in TestOps, so you would see the launch and its test results in the Launches section.
Additionally, there is an indirect connection involving defects:
• Connection between Defects and Test Cases and launches: If there is a bug-type task in the issue tracker, the connection through the defect will display in an iframe on the issue tracker side. This iframe shows all test cases that are linked to that specific task through the defect, providing visibility into how test cases relate to bug resolution.
the behaviour described above is expected and done by the system's design.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article