Standard RTC work item field for Phase Found?
Michael Taylor (88●6●57●64)
| asked Sep 09 '13, 9:10 p.m.
retagged Sep 16 '13, 9:38 a.m. by Ralph Earle (257●3●9) Our project has different phases like Design, Construction, Unit Test, String Test, System Test, Performance Test, User Test, etc. We'd like to record the phase a defect was found in. Is there a standard RTC field that is intended for this purpose? We know how to add a custom field but we want to use RTC as close to out of the box as possible for ease of setup and maintenance. We are also aware of the standard "Found In" field but understand that to be more of the Release number or build that the defect was found in not so much the phase it was found in. Is there documentation of the list of standard RTC work item fields and their intended purpose / where they are used? |
2 answers
Ralph Schoon (63.5k●3●36●46)
| answered Sep 10 '13, 1:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Sep 10 '13, 1:40 a.m.
This would be "Found in", provided you model and mark the phase as an iteration that has a release planned planned.
See https://jazz.net/library/article/589 to better understand how the default attributes and concepts hold the data together for querying and planning. Comments If you have more needs and the testing phases don#t match iterations, you could create an enumeration for the testing phases and ass a custom attribute that users need to select.
|
Jennifer Cianchetta-Riordan (251●2)
| answered Sep 13 '13, 10:56 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi Michael:
You can get more information about the work item field descriptions here: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/topic/com.ibm.team.workitem.doc/topics/t_creating_work_items_web.html. Thanks, Jenn |
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
From my experience for your use case an enumeration with a new field representing that would be the best solution. As your phases are always the same in the cycle the "found in" field would not match, because you do not want to match every phase instance with an iteration.