Ability to split defects at the end of an iteration.
by: Bill W. | over a year ago | Product Planning
Comments
Agree with Bill. We are currently regression testing and bug fixing, so mosyt of the stuff in these later sprints are defects not backlog items. I like the split ability on a backlog item, but find it strange and annoying that I can't do the same to a defect.
I know this goes beyond the scope of this specific request, but there are other areas where defects act differently than regular backlog items. Examples: Detail Tracking doesn't show progress bars for defects, they can't be associated with epics, etc.
It would be nice if these differences could also be addressed to make defects more consistent with backlog items (stories).
Agree with everything here. From my team's perspective, stories and defects are both backlog items and should be treated fundamentally the same. Though the things Rene mentioned were all problematic, the inability to split defects forced us to abandon their use altogether.
We are faced with the same concerns as well. I wonder however how to reconcile a split defect, in the case of an interface to an external defect tracking system, as we have in our case, unless the defect itself is an epic, so that a defect split in pieces still equals a single defect in reporting out of VersionOne and syncing with an external defect tracking system. In our thinking we only want to use a defect record in VersionOne for externally reported defects, defects not releated to current sprint or legacy defects. Any defect that is a regression caused by the current sprint is tracked as a task within the culprit story and therfore blocks the story from being marked as Done/Accepted until resolved.
The option to Split a Defect has been added in the Summer 2009 Release.
Comments
Agree with Bill. We are currently regression testing and bug fixing, so mosyt of the stuff in these later sprints are defects not backlog items. I like the split ability on a backlog item, but find it strange and annoying that I can't do the same to a defect.
I know this goes beyond the scope of this specific request, but there are other areas where defects act differently than regular backlog items. Examples: Detail Tracking doesn't show progress bars for defects, they can't be associated with epics, etc.
It would be nice if these differences could also be addressed to make defects more consistent with backlog items (stories).
Agree with everything here. From my team's perspective, stories and defects are both backlog items and should be treated fundamentally the same. Though the things Rene mentioned were all problematic, the inability to split defects forced us to abandon their use altogether.
We are faced with the same concerns as well. I wonder however how to reconcile a split defect, in the case of an interface to an external defect tracking system, as we have in our case, unless the defect itself is an epic, so that a defect split in pieces still equals a single defect in reporting out of VersionOne and syncing with an external defect tracking system. In our thinking we only want to use a defect record in VersionOne for externally reported defects, defects not releated to current sprint or legacy defects. Any defect that is a regression caused by the current sprint is tracked as a task within the culprit story and therfore blocks the story from being marked as Done/Accepted until resolved.
The option to Split a Defect has been added in the Summer 2009 Release.