manage defects in one place in CLM
One answer
The project area which owns a defect defines both the schema and the process for the defect, so every defect must be owned by a single project area.
The set of valid Filed-Against categories, and the set of valid Planned-For iterations for a work item are determined by the project area that owns a work item, and since these determine whether a work item belongs to a given plan, a work item must be in the same project area as a plan in order to contribute to that plan.
So if by "one place", you mean "in the same RTC repository", that is fine, because an RTC repository can hold multiple project areas (and a defect would then be owned by whatever project area contains the plan for the team that will work on that defect). If by "one place", you mean "initially in the same project area", then that is fine as well ... you can initially create all defects in that project area, and "move" a defect to another project area once you decide what team will work on that defect. But if you mean "all defects remain in a single project area", then that wouldn't allow a defect to be worked on by a team that wasn't in that project area.
Comments
If the different PAs have different process definitions (agile, waterfall and in-between), would one still be able to capture them originally in a single PA and then move to the appropriate one after triaged? I'd think not, as the form/workflow may be very similar or very different (considering what's in the source and target PAs).
For this to work then, all the project areas need to have the same definition for the defect forms and workflow. Yes, our goal is to keep all the defects for all the applications in one rtc project area for ease of access and management. Instead of moving a defect out of this one rtc area and into another rtc project area to be worked on, would it be a good idea to create a tracking work item for this defect in a different project area? Has that been done before? Thanks!