Features: Custom Fields

Custom fields

Any custom field present on a task will also be set on the copied task, if they are in the top-level of a project where those fields are assigned. Fields cannot be set on subtasks, unless they are multi-homed, so some field values may be dropped if copied without the parent project that allowed them to be set.

Custom fields are not shared between workspaces, so Ditto performs a matching step to associate fields in the source workspace with those in the destination workspace. This matching compares the name of the field and its type, including values for enum fields.

If a custom field with the correct name exists in the destination but does not have the correct type, Ditto will be unable to match the values during the copy and will skip the field. You will be warned before the transfer starts if this is the case.

Workspaces which do not support custom fields (Personal Projects and free workspaces) cannot have fields set, and so they will not be copied. Again, you will be warned if this is the case.

New Missing fields

Any fields which are used by the projects being copied but which do not exist in the destination workspace will be automatically created by copying the full custom field configuration to the destination workspace, including all enum values.

Discuss this page

Log in to comment

Brad Gregory - 27 Jul 20 19:46 UTC

another note here – looks like fields are being created redundantly still… https://www.screencast.com/t/DLyPJov5g

Brad Gregory - 27 Jul 20 19:43 UTC

Hey Michael - still getting odd errors. This time, I used the API to completely delete all custom fields and all projects in the destination before beginning, then I setup a project with a custom field, so your system would recognize custom field capability. Then I took just one group of projects instead of the entire workspace… still getting these errors: https://www.screencast.com/t/Ug8KW4L5

Michael Houston - 25 Jul 20 12:01 UTC

Hi Brad, thanks for the report - I can confirm that there was a bug where fields were being created twice, rather than being correctly mapped to the existing field. I’ve released a patch to prevent this from happening, however it is triggered when another error has triggered a retry, which may mean that you will see another problem as a result. Let me know how you get on! Mike

Brad Gregory - 25 Jul 20 02:09 UTC

Having loads of trouble here with custom fields. I have tried to delete fields, clear the values of fields, and yet no matter what I do, I get an error regarding the “Asana built-in” custom fields like “Allotted Time”. It has worked very very well for some projects but fails on this every time. I thought it might be related to trying to bring pieces of the entire org over in teams, but then I have been trying to do the entire org at once to see if that mattered. I have cleared all values assigned to this in-built field “Allotted Time” - but I cannot delete it in the destination nor the source since it is a built in the field. What am I to do? See this screenshot: https://www.screencast.com/t/CPExrZWh7rh

Michael Houston - 19 Feb 20 22:57 UTC

That’s an excellent idea, I’ll try to add that into a future release.

Anonymous - 07 Nov 19 10:12 UTC

Issue with workspaces that don’t support custom fields:

Asana’s CSV export/import will add notes to the task with the lost information, for example:

“Notes: —

Test custom field: Option 1”

It would be really nice if Ditto could do this too, maybe at the beginning of the description, or as a comment, so it’s not completely wrong.