Tracking defect inventory when opening new product version
Business Need: - When a product version (e.g. V1.0) completes development, there are always open defects for that release. - These defects may be fixed on a maintenance branch/stream and/or defered to a future version based on this version.. - We need to track this as an open defect in V1.0 that will be fixed in V1.1 AND track the defect as being opened in the new release (e.g. V2.0) In CQ/CC we would: - Branch from M/L to suppost the maintenance of V1.0 - Continue the development on M/L for V2.0 - Clone the defect to version 1.1 and V2.0 so we can track that the defect exists in V1.0, V1.1, V2.0 When we move to RTC we do not want to clone as we do in CQ today. What do you sugest? |
One answer
Firstly, I would suggest making each release as a timeline in your project area. This way you can move your work items between plans/versions as needed. Since you want to track the defect in two seperate versions, I would recommend duplicating the work item as Lily mentioned and filing it against each version (and linking the two work items as related). Otherwise, you can track that the defect (filed against 1.0, planned for 1.1) using a tag (such as backlog2.0; or something similar) to track this defect, but still storing it as one work item.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Hi Jeff,
In RTC, you can create a workitem copy with same "Found in" but different "Planned for" attribute. This is similar to the clone function in CQ.
Is there any reason you do not want to use clone in RTC?