What are possible benefits of allowing assignee to delete the task in Producteev?

When you are working in a team with flat hierarchies, this actually makes a lot of sense - the assignee can move it to another team member more qualified or remove it as redundant. This assumes of course, that your team is motivated and wants to finish the project rather than lazy and trying to skip work playing solitaire or farmville.

As some of the other posters have mentioned, it all depends on your team dynamic. I would say that if people are simply deleting tasks rather than doing them you have a bigger problem than the software you're using. Agencies that I work with usually give people the ability to delete, update and/or pass tasks as it makes it a much more fluent workflow process - you have to trust that everyone on your team actually wants to do the work though! We do provide users the ability to adjust permissions though, so I do have customers who block access to deleting things that they haven't created.

It depends on how Producteev handles "deletion" of tasks: If a deleted task is gone forever without any traces it will lead to a big mess. Even for small teams with flat hierarchies or no hierarchy. If a deleted task is only marked as "deleted" and the transition must or can be commented on everything is cool - it is transparent who deleted when a task for whatever reason. Products of characteristic 1 are for personal usage only. With products of characteristics 2 you can even experiment what works better - nothing to loose:-) I think that on the long run assignees will make good decisions of what to do delete and what not reducing workload for everybody - discussing obsolete tasks is waste of time.

Pros: anyone can fix your typos. Cons: someone can occasionally delete important information. I would turn this feature off. In software I use for tracking, you can block this feature (on premium plan).

Disclosure: I don’t use Producteev and I’ve been asked to answer this question If a team relies on principles of self-organization (), an assignee should be able to choose the most appropriate action for this task, be it working on the task or deleting it.  For example, if the task has been created by mistake, or duplicates another task, or it is impossible to complete, then the assignee should be definitely allowed to delete it without waiting for the author’s approval. Though IMHO deleting a task is justified only in case it has been created by mistake. Otherwise, an assignee should be able to “cancel” a task (I’m not sure about Producteev, but in Wrike http://www.wrike.com/it’s possible) and write a comment why the task has been cancelled. Unlike deleted tasks, cancelled tasks are still kept in the system and may be reviewed and reactivated if needed.