As weird as it might seem, there are people in #asana who completes tasks without doing them. Why?!
When you are assigned a task, you might not agree. But the work assigned probably still needs to get done. Feel free to comment back, delegate, or assign back, but please don’t complete without doing the work!
One of my clients have the workflow of using a custom field “Task accepted” with Yes/No and then the assignee should accept the task after being assigned. This way there is a strong signal to the task created that the task was assigned and accepted. It also helps with a report to find all tasks assign and not accepted in order to follow up or to reassigned.
@Bastien_Siebman I have two instances in which we mark task completed because the only other option seems to be to delete the task. (marking a task as cancelled would be preferable, but I think we would still use a task stop code to help clarify why)
The task had a shelf life that now makes it non-valuable to complete. We want to record the task was created but since we can only delete or complete we use a custom field to the show the Task Stop Code and then mark the task complete.
A list of tasks were created from a brainstorming session and these task are deemed not needed or no longer valuable enough to work on. We don’t want to delete the tasks, so again we use a task stop code and mark it completed.
OK, I didn’t think the approval process was a good one for us because when I created this work around I couldn’t see a way to filter on approvals. But now I see if I dig enough I get to approvals. I guess that would be a viable option also. Being able to search for these cancelled (completed) task and generating a list based on the (custom field) task stop codes was key when we were trying to solve this problem.