Best Practice - ReqStory, ReqTask or both
We have a dept that has been linking Requirements to Stories to Test Case.
That has worked fine until the most BASIC question was asked by the business: What happened to that feature/requirement we asked for? We can't show the build that the feature went in because it was done by the tasks. Of course the Tasks done for the Story are linked to the builds. So, is the best practice to link just to the Story, the Story and the Tasks or just Tasks? |
One answer
Mahari,
you can answer that question easily from RTC by opening the Locate Change Set Wizard. In the upper part drag/drop all stories from the requirements you are about from a query result windows. In the lower part drag/drop the build result objects into the Locate Change Set Wizard you want to know about. As a result the LCS will show you (using the change sets linked to all child tasks of the stories) which change sets are included in which build, i.e. in which build the requirement(s) are included. So my suggestion is to keep linking requirements to stories as their implementation items. If this answers your question please mark this as accepted. - Arne |
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.