How-to: group epic/story-related defects in RTC 2.0
Hello,
Currently, we have an environement in which RTC/RQM/RRC 2.0 are integrated. As result: Use Cases in RRC are exported in RTC as Epics, Scenarios in RRC are exported as Stories in RTC and then Collections of scenarios (per use case) in RRC are used as input for test plans in RQM. Once test plan in RQM are used and end in identification of defects, tehse are injected in RTC.
Unfortunately, today, we get a list of defect (cretaed rom RQM) in a RTC backlog but encounter difficulties to know to which story/epic a defect belongs too. This is a traceability problem. We were thinking of using tags and then in RTC have a mode in which the grouping is based on tags but this becomes a heavy process.
Any better idea? Or is this addressed in RTC beta2(3/GA)
Thanks in advance.
Regards
Currently, we have an environement in which RTC/RQM/RRC 2.0 are integrated. As result: Use Cases in RRC are exported in RTC as Epics, Scenarios in RRC are exported as Stories in RTC and then Collections of scenarios (per use case) in RRC are used as input for test plans in RQM. Once test plan in RQM are used and end in identification of defects, tehse are injected in RTC.
Unfortunately, today, we get a list of defect (cretaed rom RQM) in a RTC backlog but encounter difficulties to know to which story/epic a defect belongs too. This is a traceability problem. We were thinking of using tags and then in RTC have a mode in which the grouping is based on tags but this becomes a heavy process.
Any better idea? Or is this addressed in RTC beta2(3/GA)
Thanks in advance.
Regards