Mark Sections as Complete (in new spreadsheet List view)

NEED: The ability to mark a section as complete so it no longer appears within a project when filtering for incomplete tasks. AND to be able to do that without deleting the history of tasks within that section.

SUGGESTION: Add an option to sections and boards to either a) complete the section as you would a task, or b) archive the section as you would a project.

*Please do not conflate this issue with the need to be able to delete a section. These are two related but fundamentally different issues. Also, this issue specifically relates to the new section layout.


1. Basic Functionality

This is very basic functionality.

When a task is completed, it can be marked complete. I can review completed tasks by filtering for ‘All Tasks’.

When a project is completed, I can archive it. I can review archived projects by clicking on ‘Show archived projects’, within a given team (that bit is clunky, but at least the data is there).

The new sections are great in many ways. But they can neither be completed nor archived, which is silly.

2. Delete Isn’t the Answer


An important basic function is the ability to review previously completed tasks.

We need that data:
a) to track the progress of work,
b) to reference details contained in attachments and comments on completed tasks, and
c) sometimes to copy a completed set of tasks as a template for new work.

3. Current Hacks

The hacks we’ve identified to manage this issue in the meantime are as follows:

a) I can delete the section.

That removes it from the project view but eliminates all historical data. *Currently sections can’t even be deleted without first deleting all the tasks within it. That is even more silly. I understand there is a fix in the works to resolve this. That’s good but DOES NOT SOLVE the issue defined here.

b) I can create an ‘Archive’ section at the bottom of the project, move all completed tasks there, and then delete the old section.

This removes the section from project view and preserves the data of the original tasks. But now the tasks have lost their structure that we took pains to define through the way we set up the sections in the first place. I’m left with a giant pile of random tasks inside an Archive folder I’d rather not have cluttering my project.

c) I can create a task within the archive that has the name of the old Section. Then I can move all the tasks from the old section into subtasks in the new task within the Archive section. Then delete the old section.

That still leaves me with an unwanted ‘Archive’ section in my project, but at least it is just one unwanted section and the order of the tasks and associated data is preserved. But really? Man that is an unreasonable amount of tedious administration.

Those are the current options we’ve been able to identify. Are we missing anything?


Hi @Antoine_Palmer, we have an interesting #productfeedback thread (Archive a Section in a Project) requesting an option to Archive Sections so if you’re ok with it, I can merge it to consolidate feedback on this topic and help the Community voice to have maximum impact!


Please don’t. I appreciate your point but that thread is confusing as it relates to the old sections layout and addresses a somewhat different issue.

I’ve already given my vote to that thread. I see what you mean but I believe the distinctions are important.



Highly agree with everything you have said. Cannot believe the new version has meant losing this functionality, along with having overarching task information being able to be stored with the section header.


We use sections extensively, but we complete sections & don’t want them to show forever. I used to be able to mark a section complete (similar to a task). Recently, I noticed that this option is no longer available. This severely impacts our ability to use Asana efficiently.

It looks like my only options are to delete the section (which would also delete the associated completed tasks, which we do not want to do) or rename thes ection, which isn’t what we want to do either.

I totally understand how, from a programming perspective, it might make sense to take away the incomplete/complete attribute from a section (that really is more of a task attribute.)

But I need a way to have the section exist in the history without it polluting my view of current tasks.

Can you please let me know how to accomplish this? If it’s not possible with the most recent updates, can you please consider adding a “Hide Section” option as a high priority feature request?

Also responded under New Section Dilemma discussion in use cases, New Section Dilemma - #4 by Sara_Dunn


This has also greatly impacted my workflow. If we can mark Projects and Tasks complete, we should be able to mark the step between them (Sections) complete or hide them. Asana, as a productivity program, should understand that there are always different reasons why that kind of feature may be needed. The fact that the update removed a feature is the opposite of productivity.


Same as everything said above. I would like to be able to mark a section complete and keep a link to its tasks in the completed tasks view. I don’t really want to delete the section and I definitely don’t want to have to remove all its completed tasks in order to delete it.


Completely agree with the above sentiments - we regularly used the “Mark Complete” function on Sections, Deleting sections (and all contained tasks) is not a viable option as we do regularly refer back to completed Sections. Can this feature be reimplemented?


Hi there,

i am not sure if this is discussed somewhere else already - i didn’t found any matching threads to my issue.

We recognized in the past two days, that you guys made some changes on Sections in projects. We are not able to “complete” them anymore as we do this on tasks. If we work with projects we always consider in which step a task should be arranged to. the step is displayed as a section in asana. once all tasks, related to its “step” are done, we will complete the section.

now - this is not possible anymore. I am only able to “delete” the section - and surprisingly ALL tasks related to this section. Why? Who wants to have a feature where i am able to delete by accident a full load of information?

Is there a chance to receive - someday - an option to “hide” fulfilled sections in the project? currently i just move them to the bottom of the tasklist to get them out of my mind and focus on the important tasks.

Greetings from Berlin


Hi @Maik and thanks for sharing your feedback with us. we already have a thread on this topic, so I’ve gone ahead and merged your post to gather all feedback in one place.


thanks a lot, Marie.


Any info on whether this is being looked at? Since the switch in Sections is relatively new, I would hope this issue would be seen as a missed problem related to that roll-out and maybe get higher priority. It is quite problematic for using Sections, because more often than not we finish out a section and then want to Complete the section as well.


Thank you, Antoine, for a very clear and cogent definition of the problem and a list of currently known workarounds.

Now, if we only had you and another 20 of our best forum commenters sitting in the Product Development war room at Asana, we could really get some improvements done.


The most confusing thing is that it is really unclear what a Section could plausibly be used for now. It seems like Sections should be semi-permanent inside a project. In which case, what are you supposed to use inside a master project, which is a recommended workflow by Asana to keep a view on multiple projects at once? You don’t want to have temporary Sections for subprojects, because you cannot complete them and don’t want to delete them when the subprojects are finished. You don’t want to have permanent Sections representing active tasks, or shelved tasks, or due dates or anything, since that is what properties and priorities and due dates are for. What is a Section good for now? I’d appreciate an example of what kind of workflow the new Sections are supposed to support.


The solution seems obvious…make Sections completable. Just like their parents - projects - and their children - tasks and subtasks.

What are the possible downsides of completable Sections? I’m going to assume that we want the behavior of not allowing a Section to be marked Complete if any of the Tasks or Subtasks are not complete.

Come to think of it, since Sections are entities within this large database known as Asana, we will need to be able to search for them. Right now the stated choice of entities in Advanced Search is

All * Tasks * Conversations.

In truth, one can search for Projects, Tasks, Subtasks, Tags, and contents of Custom Fields (if the not the field names themselves), but apparently not Sections. I would like to offer a rule of thumb to Asana designers and product managers; in general, if the customer goes to the trouble to create an item of data or an entity, they would like to be able to find it, and that requires Search.


Just going to pile on here and say that we need the ability to mark sections as completed like it was before. And I’ll repeat that visually, I miss the solid line going across the screen separating sections. It was easier to read and just like an excel spreadsheet, I’d like the option to retain that border.


I agree with your idea Sara. I’d love to be able to hide sections where I’ve completed all tasks (I think I use sections in the same way as i do). Being able to set “due date” which I could mark as complete was very helpful.


Hahahahaha. Thanks Stephanie! For the record, with a couple months advance notice, I’d be down for a war room retreat/ :wink:

1 Like

In agreement with all of the statements here. I’m not sure why this was ever changed and why it hasn’t been fixed. Let us mark sections complete!


Have any of you heard anything on this? Or are we all equally in-the-dark on whether Asana is doing anything about it. This is proving to be EXTREMELY problematic for my workplace and multiple other organizations that I use Asana with… and I’m feeling like the issue is falling on deaf ears, which seems to happen a lot.

1 Like