Requests vs Tasks/Projects

Requests vs Tasks/Projects

We have a senior administrator who believes that the number of open requests is the KPI of a tech department. We're working on changing that, but in the meantime we need to find a way to separate Requests from Tasks/Projects. For example, "my printer is repeatedly jamming" may be a request, but "deploy Vista-capable printers" or "reinventory hardware" aren't support requests; yet we need to keep track of that list.

Question 1: How is everyone tracking the task/project type issues? Are you using just the Tasks part of SD+? (We're using SD+ Standard.)

Question 2: Is there a quick way in SD+ to convert a request to a task? I'm guessing not, since the object schemas are so different.  We have probably as many as 30 requests that should be Tasks/Projects/Whatevers.

 

                  New to ADSelfService Plus?