Or have a task in the backlog called “Archived tasks” and move a task as a subtask of it when archived. But a project is probably better.
You can also add a tag (I think @paulminors shared something about this recently) and then if you want to see archived tasks you can run a search for completed + having the tag.
Thanks for the suggestions!
I agree with @lpb on moving them to a projects called ‘Archived Tickets’. I think it will keep a clean workspace in your other project, yet keep the archived ones readily accessible when you need them.
Good luck!
Katie
I wanted to bring this topic into light again since I thought of another unique way archived tasks might be helpful.
I run a small library (2.5 FTE) where we have various ongoing tasks and essentially projects with no end. For example, our Collection Development project has tasks related to quarterly shelf upkeep and catalog maintenance. We move through the tasks and continue to add more but the project of Collection Development never end. This process works fine…if you stay in Incomplete Tasks view. Once you select All Tasks view, your hit with an entire backlog of completed work.
I still want to keep those completed tasks for the valuable data, general reference, and running reports. The solutions so far add a bit of busy work after the completion of the task and I want staff to feel the accomplishment of hitting that completed check mark. An archive task feature that would help me tidy up the back end while keeping staff engaged and without sacrificing the data. This would really help with maintaining routine business operations long-term.
Though as I was writing this I thought of a rule addition that would auto move tasks to a completed task section so maybe it’s mote at this point… 
I’ll keep what I’ve written since someone else might find it helpful, too. 
I’ve created several tasks under a project and I would like to archive some of the tasks because the list has become long. Again, I don’t want to archive the project but just a task under project. Could you help me suggest how to do that?
Hello @PANUGANTI_RAVINDER,
is there a specific reason why you would like to archive them? Only displaying incomplete tasks in that project won’t help?
Otherwise what you can do is set up a rule in that project that every task that is being marked complete is moved to a special project that just has a collection of completed tasks.
I also recommend voting here: Ability to archive tasks.
I wish there was a way to “close without completion”. There are tasks I thought we’d have time for, the time has now passed and we didn’t have capacity and so we did not do them (e.g. testify for a public hearing on a set date).
Marking this kind of task as “completed” makes it appear as though we DID testify, when we did not. Today I can “delete” the task, but then we lose the transparency into analyzing capacity issues we might have, not to mention the record of what we had to say “no” to (something we do track as well).
What I am using now, thanks to @lpb , is turn the task into an Approval and then reject it.
Hi community,
Fairly new here. Our team has also been experiencing some frustrations in regards to archiving tasks. We work with ongoing projets which sometimes have no “end” date, and we see tasks beginning to add up quite a bit in these projects. It would be really useful if we could archive or even hide these tasks, both in “Projects” and “My Tasks” 
@anon51278683 don’t you complete those tasks eventually? Do you need to show completed tasks?
@Bastien_Siebman sorry I was referring to completed tasks that we would like to be able to archive - not delete, in order to be able to keep track of everything that’s been done over the months/years for a specific project.
And why not hide completed tasks using top project filtering options?
Sounds like a very viable option ! Is it included in the free version ? Maybe that’s why I’m missing it ?
This is definitely available in the free version, search for the “All tasks” button at the top of a project.
Yes…there should be canceled or hold options for tasks that Asana recognizes. Yes, a custom field can be used for this but Asana does not pause the due date.
Also a Canceled option for Project Status for that matter. Otherwise reporting is skewed.
Feature could probably have been implemented in less time than it has taken to write all these explanations about why it is not implemented and how you should work around the missing feature.
This is not that simple. A tool is not a collection of features piling up. Otherwise you end up with Salesforce and need a consultant to set it up.
Archive or mark as done with explanation is needed here. When you delete a task you lose the history of partial work done. We regularly start a task and then decide later it may not be needed - it isn’t “complete” so that feels wrong to check. It is “not done” for some reason and deleting lose all description, comments and history.