Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have recently started to use TFS and are using the MSF for Agile v5.0 Template. Tasks that I have created seem to only have 2 states. Active and Closed. In reading the documentation that I have found … it shows that there should also be a "Resolved" state so that when developers are finished they can mark it Resolved and then once the task is tested it can be marked Closed.
Can somebody help me understand what I’m missing? Is there a step I’m missing in the process?
Assaf Stone’s answer is an accurate solution for part of the question I asked, but I understand now that I really was “Missing” something.
After spending time with TFS, I figured out why they removed the “Resolved” state from Task. A task should be linked to a user story and As a user story is where the testing or next step would be. A task does not need a “Resolved” state.
Now if you wanted to add an additional step for a task such as “Code Review” that would be valid but there is not a need for “Resolved” on the Task itself.