Custom fields empty after moving tasks from one project to another

English Forum Tips and Tricks
1

Briefly describe (1-2 sentences) the bug you’re experiencing:
Our team creates a new project for every sprint. In order to do so, we duplicate the current project minus the tasks. Then we move the tasks from one project to the other. Why do we do this? While duplicating the entire project doesn’t reproduce the same bug, it would also duplicate the tasks. Then (1) we’d have to go back and delete the originals in the old project and (2) we lose the task history.

Steps to reproduce:

  1. Duplicate a project (all attributes except tasks).
  2. Move the tasks from the old project to the new one.
  3. All custom fields are empty, even though they have the exact same attributes.

Browser version:
Not applicable (desktop)

What version of Asana are you using (Personal, Starter, Advanced, Enterprise, Enterprise+, Premium, Business or legacy Enterprise)?

Enterprise

Upload screenshots below:

2

Hello @Nicholas_El-Khuri,

Are you 100% sure that “All tasks” is un-ticked. I just tested it here and was able to duplicate a project with all attributes except existing task. All I did is ensuring that “All tasks” was un-ticked.

Could you create a dummy project with a bunch of tasks and let me know if you can replicate with this dummy project? If you could grab screenshots (or even better a video) showing what you experience, it would be super helpful!

5

@Marie while I sort of get why this might work this way, it’s just not great when we want to preserve the integrity of tasks. There are several other use-cases for duplicating then moving tasks, for example projects shared by several people that track things separately: it wouldn’t make sense to have the same custom field in both projects, but instead a shared custom field which updates when the other does. Worst case you create a new one if you need it, but by default they should sync.

6

@Nicholas_El-Khuri is your Custom Field added to your Organiszation library? If it is, you should be able to move your tasks in the duplicated project without duplicating the custom field.

7

Hi @Marie ,

Here’s an example with a dummy project/task.

  1. Dummy project created with one task and two filled out custom fields.

image
image1355×335 21.4 KB

  1. Project duplicated without tasks.

image
image616×847 21 KB

  1. Empty new duplicate.

image
image1305×348 20.7 KB

  1. Task moved to the new project.

image
image717×341 14.2 KB

  1. Custom fields empty.

image
image1278×383 21.8 KB

  1. Task details where the issue becomes more clear.

image
image700×520 16.7 KB

8

@Marie apologies for the spam I wanted to consolidate and made a little mess.

I think the custom field is private to the project. It does show up when I make a new project though.

1 Like
9

Ah this seems to have solved it. Is there a way around this?

10

Not that I’m aware. Adding and using custom fields from your Organization library is the only way to ensure your custom fields are synced across your projects. Note that when adding custom fields to your library, you can still set them up so no one else than yourself can edit them.

11

Thanks @Marie

1 Like
12

No problem @Nicholas_El-Khuri, you’re welcome :slight_smile:

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.