when running a test, if you hit a bug, or several, you should be able to associate it with that result. And if you associate it with the result, it should also be associated to the testcase for that result.
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/15473317
What fields would you like to store for this association? Just a bugId or something else?
BugId would likely be enough, but a description field might be very useful as well. we may implement tighter Bugzilla (or other system) integration later that would pull in the bug summary, but likely not in 1.0.
I think if the initial goal is to be bugtracker-agnostic, the most critical field to have is "bug URL" rather than "bugID". This means the bug can actually be linked to from within Case Conductor. Any field besides URL is likely to be specific to a certain bugtracking system. Would a "description" field actually be useful, or would it just end up being a needless duplication of information that has already been entered in the BTS itself?
agh, you're right. Bug URL is what we need. Description may be a duplication, yeah. I mean, I could see it being a short hand to help the person find the right one, if there's several bugs. But it may end up just being un-needed cruft. I'm totally fine with just the Bug URL.
Added endpoints to testcases and test results: https://localhost/tcm/services/v2/rest/testcases/2/relatedbugs/ Also, added generic endpoint for external bugs handling https://localhost/tcm/services/v2/rest/externalbugs/1/ See WADL for details
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.