Issue tracking in Jira — how do you keep it connected to your test cases?

Question

We use Jira for issue tracking and Tuskr for test management. When a test fails, we create a linked Jira issue directly from the test execution, so it's easy to trace bugs back to the exact test case and retest after the fix.

How is your team handling this? Happy to hear what workflow has worked well for you

Ashik Muhammed _ AIO Tests · Answer

The test-to-defect link covers the moment a test fails. What's usually missing is the same link read backwards - opening a story and seeing its test cases, the latest result for each, and any open defects, without assembling that from two places.

An equally important question is "has this requirement been tested, and where does it stand now" - and how quickly can it be answered?

Also important is the ability to see execution history per case across cycles rather than only the latest run, which matters most for regression across releases.

Full disclosure: I work on AIO Tests, which does all this inside Jira.

Arkadiusz Wroblewski · Answer

Hello @Vinayak Wagh

Across Atlassian Users, i think Xray is most popular with long history.

Marc -Devoteam- · Answer

HI @Vinayak Wagh

That would depend on the Test management solution used.

Different tools will handle this isn a different way, but be default this shoul be the way in my opinion.

I have used Xray most of the times and here you can also create an issue of a configured type based on test failure or even test step failure (if using manual testing)