"Not Needed" "Not Doing" vs "Completed"

I often create (“stub out”) tasks that I think I’m going to need for a project. Often there are some the end up not being needed for one reason or another. I’ve either just marked them complete (which isn’t really right, but it’s easy!) or deleting them.

Is there a way to set the task to some other status to keep it, but still know it’s no longer in play? Or do I just delete these unneeded tasks. (And if I do end up needing it in the future, I’d have to recreate it.)

1 Like

Hi @anon59828738, thanks for reaching out!

This is a good questions! You can create a private project to save those tasks instead of deleting them from Asana. By doing so, you will be able to use them in the future if you need it!

You’ll simple need to multi-home them in the private project and then remove them from the original project. You can also select several task at the same time with the multi-select feature.

Alternatively, you can also add custom fields or tags to the tasks so you can have a better overview of the tasks that are “not needed” or “not doing”.

You are right, it’s currently not possible to mark a task as “not needed”, “not doing” vs “Completed”. You can add a vote to a similar product feedback here: Reference-only Tasks that can't be marked complete

I hope this helps! Let me know if you have any follow up questions :slight_smile:

1 Like

I think the custom field is the best approach. A separate “private” project creates too much disconnectedness. You’d lose context of a variety of “not doing” tasks from a variety of projects. Thanks for the quick reply.

2 Likes

Good point @anon59828738! I agree with you :+1: