only creator of task and project manager can set status to approved or closed

I disagree that the creator of a task can set the status as approved/closed. You should either be a project manager or have an explicitly authorization for that. I understand that each studio uses a different work-flow for bug/task, I never heard a place where people can approve their own bugs... what kind of "approval" would that be?

Actually, I don't know, if we need this setting at all. In most situations the project manager should check the changes in 'his' project anyway. If somebody approves a task for himself, this is listed in the recent changes and the PM will see it.

There always could be reasons, where closing/approving a task without bothering the PM might make sense.

Ganesh: How important is this feature to you?

Well... it depends on the number of bugs that you are managing. I worked on projects were, in the "hot" periods, we had several dozens of bug open and closed every day. I can't think a PM could properly follow all that, nor that he/she should. In fact we had a specific person (either the Lead Tester or the QA Manager for even bigger projects) responsible for that task.


Yes, there might be reasons. But really this is a field where you can never customize enough ;-)

Other tools I used in the past have implemented a very customizable bug/issue workflow, maybe we should look in that direction too. I feel this feature is quite important, albeit it's not so urgent at this stage of the Streber development. I think we should allow ourself some time to think about it throughly.

I once heard the slogan: