Different configurations for Tasks

I would be a really great improvement to be able to create different workflows/security schemes for tasks. At least in my company, tasks do not work the same as bugs. Developers use taks to track items that need to be completed for a project. There are 3 issues with this

1) The workflow is differnet from a bug, something like (open, InProgress, Finished) would seem more approriate. The problem is that there is no "breaking up" of issues and this workflow will not work for bugs.

2) One rule (which I believe should remain in place) is that only the testing group can close a bug. The problem here is that tasks are not bugs and testers have no idea if a task has been closed because in most cases there is no way to verify the competion of the task.

3) Tasks show up in the release notes for the project much in the same way that bugs do, but tasks are not the same. In fact, most tasks should not be in release notes.