Move/Copy entire Sections from one Project to another Project

We would love to be able to move entire Sections (i.e. the Section and all the Tasks under that Section) from one Project to another Project. This could be either a MOVE option or a COPY option. The absolute best would be to have the option to do either a MOVE or a COPY.

I think the methods that would be easiest for Users would be:

  1. Click and drag an entire Section into the side-bar and drop it into a different Project (have a “Move or Copy” pop-up)
  2. Have a menu pop-up on a Section that has an option to Move or Copy to another Project

Currently you can’t really “select” a Section, which means you can’t multi-select Sections and move them together, even within its own Project. You can drag it within a Project but that’s it.

Current Work-Around: Go into the destination Project and create Sections that correspond with the origination Project. Return to the Origination Project and multi-select all of the individual Tasks in that Section. On the side-care you can select where those Tasks live, allowing you to select the destination Project/Section. Then you can remove the origination Project. This simulates a “Move Section” action.

Use Case: We have various Projects with Sections that are beneficial for a new Project that might emerge, and it would be easiest to copy over the whole Section. Example: part of an overall Project might be a Section for “Conduct User Training” with a bunch of Tasks under it. But doing training ends up being a part of a ton of Projects we have so it would be so convenient to just take that Section from another Project and copy it over into a new Project where we know we’ll need to do “User Training.”

Another feature that I think would be even more valuable would be to allow the copying of a section to another project so that the two projects mirror each other, including with the addition of new tasks in the future. Thus, after coping a section from one project to another, if I add a task to that section in one project it automatically adds to both projects. As it stands, I have to manually make sure that the tasks remain the same between the two projects, which it quite a pain.

3 Likes

Welcome to the Community @Jeremy_Newman!

This is probably a good illustration of why development is so challenging - because I understand what you’re describing, but for us that would actually cause major issues. So in one use case it makes sense, but in another it causes problems.

If I’m understanding your request, you would want to copy a Section from one Project to another, and potentially another, and another… and then adding a Task in one Section in the original Project would add it in all the others.

But let’s say I have a Section called “Website Stuff” and every time our Marketing department has a marketing campaign, we create a new Project and then copy the Section “Website Stuff” into that Project. That Section would have the basic “template” Tasks but there would be lot of specific things that would come up, and we would only want it added to that Project (campaign), under the Website Stuff Section. It would tie things together in a very unwieldy way for us.

Could it be made optional so that tasks could be tied permanently to the section header or allowed to be separate? That way only the tasks that you wanted cloned would be cloned.

1 Like

The ability to move entire sections from one project to another would be extraordinarily useful. And it seems obvious. I’m a new user, and it never occurred to me you would not be able to. Since the “board” layout presents each section like a Trello “list,” and the underlying attraction of this format is the drag and drop functionality, it seemed a fair assumption that whole visual “section” structure could be moved to another project.

I’m a little bit stuck now, unless anyone has a suggestion: As a new user, my goal with Asana is to take an enormous number of totally unorganized tasks and create a project structure that works. So I created an excel document of hundreds of these tasks, and running down the list could assign each of them a “section” in the excel document. I then exported the CSV to Asana. My thought was I would then have all these visual columns (sections) aggregated in one project and could see how best to group different ones into their projects, moving them around fluidly. But no, and I’m crying a bit inside.

Any workaround ideas? I’ve been editing things in Asana, so I cant go back to the original excel doc, but I suppose I could export this Asana project, reorder it in excel, and then export each “section” of tasks back into new projects in Asana. Other thoughts?

And slightly off topic: any idea why Asana basically seems to ignore the existence of sections, in general? I’m finding difficulty with searches, and with creating them.

4 Likes

I cannot say how important this is.

Projects evolve and I expect my task manager to be able to keep up with that.

Sections are a huge part of Asana.

What was once “Recurring Content” with a few sections as it’s own project, now needs to be split into multiple projects within the team because it’s grown. Fantastic, but I can’t do that in Asana without retyping or dragging each individual task that was in that original section.

It’s just not reasonable as it is now.

2 Likes

We have 3 separate projects, Customer Feedback, In Development, and Past Releases.

We use Customer Feedback to prioritize our development effort, and we move all the feedback that will be incorporated in the next release cycle into a single column.

We would love to be able to easily move this column from the Customer Feedback project to the In Development project.

Once in In Development we move the tasks through Currently Implementing, Ready to Push to Staging, Ready to Test, and Ready to Release columns.

After a release it would be great to move the Ready to Release column to the Past Releases project, where we then add the release date to the column name so we can track when we released certain features.

The ability to easily move a column from one project to another would clean up our projects, help us stay organized, and save us many hours every week.

Hi @Steve_Johnson,

I’m always a little hesitant to respond to threads in Product Feedback with workarounds because I feel it sometimes muddies the water for people looking for votes and are already aware of workarounds. If you’re interested in a fairly easy way to do this using Advanced Search, let me know.

2 Likes

Thanks for your feedback @Steve_Johnson and welcome to the Forum!

As it stands, we don’t have an option allowing you to easily move a column from one project to another, however, I can see how useful it would be for you and your team. We will definitely take your feedback on board for future improvements; thanks again for sharing your feedback with us and for taking the time to provide us with context too!

As @RyanE mentioned, there is a workaround (see below) you can use, but I hope we can simplify this process in the future!

Workaround:

Project A: Project where tasks are currently located
Project B: Project where you want to move your tasks

  1. Open project B and create a new column
  2. Open the Advanced Search and run a Search for all tasks nested in project A column (you can easily filter tasks by adding Project A in the “Project” field and select the relevant columns in the Project drop-down menu)
  3. Multi-select all tasks
  4. Open the project field and add these tasks to Project B (make sure to use the drop down menu to select the column you created in Step 1
  5. While you have the project field open, remove Project A from the Project field, this way your task will appear in Project B but not in Project A anymore!

Hope this helps!

1 Like

Thanks! That helped me clean up my existing projects :slight_smile:

1 Like

absolutely critical in may operations. My project templates are really big… so if I could copy sections let’s say from a template, we could re-engineer and start with smaller template and build up based onthe master template. Also as a potential, if we could copy multi-selected tasks to another project, not just a single one, that may solve the problem half way. Thanks

1 Like