We use Jira for tracking stories, bugs, and development work, and I’m trying to understand how other teams keep Jira issues connected with their testing work.
I’m currently working with Tuskr for test management, so I’ve been exploring how the Jira integration can fit into our workflow. What I like about this kind of setup is being able to keep the test cases and test runs in a test management tool, while Jira continues to be the main place for development issues and bugs.
For example, I’m looking at a workflow like this:
Jira story → related test cases → test run/result → Jira bug if something fails
One thing I’m trying to decide is how much information should be connected back to Jira.
For example:
- Should each Jira story be linked to the relevant test cases?
- Is it better to link the test run instead of every test case?
- When a test fails, should the tester create a Jira bug directly from that result?
- How do developers quickly see whether a story has been tested and whether it passed or failed?
I’m using Tuskr at the moment, but I’ve also been looking at how tools such as TestRail and Xray handle similar Jira workflows. I’m not really trying to compare which product is “best”; I’m more interested in understanding what works well for teams in day-to-day testing.
For those who use Jira with Tuskr, TestRail, Xray, or another test management tool, how do you normally keep everything connected without making the process too complicated?