Removing sections from tasks

tasks

#1

Hi, I am just starting to learn Asana. I have done something weird and now I have sections on tasks that just makes everything messy. Is there a way to remove sections?! 35|436x336

I am duplicating the main task and using it as a template, so this just makes millions of the same task.

Thanks


#2

Are you talking about sections in Projects and your My Tasks? They’re basically normal tasks that have a colon on the end. You can delete them just like any other task by selecting them, clicking the … icon and selecting delete (or TAB+BKSP as a keyboard shortcut) or get rid of the colon at the end of the task’s name to convert them back to normal tasks.


#3

35 No, I’m talking about… sections and projects I think. I tried attaching a screen shot. It is at the top to the left. I think i have multiple projects listed, and i don’t want it like that as it is multiplying whenever I duplicate it…


#4

Attaching another screen shot to show how it is multiplying. I want to get rid of where it says client in pink :slight_smile:


#5

From your tast screenshot, what I can tell is:

  • the task is hosted inside the “Wedding client workflow” project
  • it is also hosted inside the “Photo blog post” project
  • and it is under the “client workflow” section

Does it help?

Bastien
Asana consultant, author and developer


#6

It looks to me like subtasks and copying tasks might be the source of confusion.

Adding a project to a subtask will make that subtask show up as its own task in the project view instead of limiting its visibility to only within the parent task. If you then copy a parent task (I see “duplicated task from …” messages in the task history) the copied tasks and subtasks will have the projects assigned in the same way (the copy screen lets you change this behavior). This means you end up with a bunch of copies of the same task up at the project level and no easy way to tell them apart.

So in your screenshot, on the right-hand pane, the “Skrive blogposten - 3x3 - nevne vendors” is a subtask of the “Photo blog post” task which is the subtask of the “Wedding client workflow” parent task. In the left pane all the subtasks are the ones that have gray text to the right of the task name and this means all the subtasks must have been assigned the “Clients” project as well to show up there.

Typically I prefer to not add subtasks to projects just for this reason. If I do, I tend to go through and put info in the subtask’s name to differentiates it from other subtasks with the exact same name.

Here’s an example of mine:
I think I have a project that does something similar. I have a template project called “Templates” where I have a set of tasks with subtasks:

When I copy this task, I always rename it (hence the [insert view name] in the title). I also include instructions on how to handle the template tasks in each one so people know what to do when they get one of these.

There’s a lot of built in subtasks that have subtasks of their own. In this one the main task is two tasks deep (subtask of “create doc…” and “TEMPLATE: Create query…”):

I do tend to add these subtasks to a project, but only as I assign them to individuals and they become “workable” otherwise they clutter up the overall project and I only want to see work that needs to get done, not work that’s nowhere ready to show up. When I do assign these subtasks, I also add details to them that makes it so I can differentiate between them in the project view:

Hopefully this gives you some info on why you’re seeing so many tasks in your project and also how to manage them.


#7

Bravo! I stared at the original screenshot for ages trying to figure out what was happening and I couldn’t get my head around it.

Nicely done. :clap:


#8

Thank you! It does kinda make sense, but at the same time I don’t understand why I ended up with 12 duplicates when I only copied it three or four times… Anyway - I deleted it all, and am starting over. Still working on finding a good way to make my template into each new client. I think I will try using tags to separate them. Although it looks like I manually have to add tags to each subtask - which sucks.

Thanks again. i will probably have to refer to your reply many times before I completely understand it :slight_smile:


#9

I find subtasks useful, but they tend to complicate things and I often end up in a state where I want to constantly rework them as I gain clarity towards the end of a parent task and realise my initial impressions of what I’d need to do evolves. For repeated tasks that need a process they’re very helpful and I can update them when things change.

I’ve also seen quite a few people post about setting things up based on clients on the community here. If you haven’t searched yet, there might be some good info, I found the following: