Right now defects cannot be associated with an epic. It would be helpful in organizing defects better if they could be - like backlog items - be attached to an epic as well. This would close another gap between behavior of defects vs. backlog items.
by: Rene R. | over a year ago | Product Planning
Comments
More Detailed User Story:
As a VersionOne Product Owner I want to be able to link Defects to Epics so that I can create a high-level epic to group a set of Planned Technical Debt during a release. Right now, only Backlog Items can be related to Epics.
For example, one of my quarterly service pack releases might have a goal to spend 30% of my points allocation on reducing technical debt. I want a rollup epic, "Reduce Technical Debt," and be able to link all the planned defects under that epic. This issue affects all Product Owners and Scrum Masters (60-70 people in our enterprise system, and hundreds of defects in each release project).
This is a must for us, as we like to have "clean-up areas" as epics. Being able to associate defects would be more efficient for us than creating new stories or projects.
I would like to tie my defects to EPICs the same way I do with my user stories.
Tying defects to epics the same way as user stories will enable us to better track customer requests and problem reports.
I second Judy's request. I want to monitor the health of the epic (defect density, leakage) & take corrective action asap.
You can now associate defects and test sets with Epics in the Summer 2012 release of VersionOne.
Defects and test sets can be associated with an epic by editing the field in a grid, editing through the lookup, or by using the new multi-select Move To Epic option on the Backlog page in Product Planning.
Please see the release notes for complete details of the Summer 2012 release:
http://community.versionone.com/Release%20Notes/ReleaseNotes2012Summer.aspx