We actually find more use using remote linking and activity streams for our own internal process. The reason is that we drive our testing based on issues that we import from JIRA as requirements. We have a few triggers that we create in QMetry that will automatically pull JIRA issues once the trigger has been met. This ensures that all issues that meet our testing requirements are pulled in, rather than relying on an issue by issue manual process.
Once the JIRA issues are pulled in as requirements they are kept in sync with the JIRA issue and the JIRA issue will have a link to the requirement showing the coverage status. Our QA team then can build functional test cases directly against the requirements, and/or link existing test cases to complete the coverage. The test cases added to the requirement are automatically added to the JIRA issue so development can review the test cases and see their testing status as testing begins. This process has greatly improved our coverage, and the improved communication between development and QA has helped speed up deliveries for us internally.
I hope this helped explain a bit about how our integration works. Let us know if you have any questions.
David Silva | QMetry Product Manager
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs