S
Steve Lundwall
Realizing that Project and Project Server are not good 'HelpDesk' tools,
nonetheless, I have been directed to attempt to create a business process in
which significant help desk items are assigned to an overall Help Desk
Project as tasks. That being the case, (we use the daily hours tracking
method) is there a way to prevent a task from appearing complete simply
because the developer resource reports time against it that matches the
estimated time? We want our QA person to test the 'fix' and say it is
acceptable.
Would this require assigning two resources to each task - the developer
resource for a big chuck of time and the QA resource for a very small chuck
of time? What we don't want happening is if in the original review it is
estimated to take 10 hours, that if someone - anyone - reports at least 10
hours that it appears 'completed'.
Thanks.
Steve
nonetheless, I have been directed to attempt to create a business process in
which significant help desk items are assigned to an overall Help Desk
Project as tasks. That being the case, (we use the daily hours tracking
method) is there a way to prevent a task from appearing complete simply
because the developer resource reports time against it that matches the
estimated time? We want our QA person to test the 'fix' and say it is
acceptable.
Would this require assigning two resources to each task - the developer
resource for a big chuck of time and the QA resource for a very small chuck
of time? What we don't want happening is if in the original review it is
estimated to take 10 hours, that if someone - anyone - reports at least 10
hours that it appears 'completed'.
Thanks.
Steve