Hey,
I’ve set up an asana rule to add a task to another project if the task is overdue. Updates made to custom fields in the original asana project is not being reflected in the new project that the task is added to. Is this a bug or am I missing something?
1 Like
Hi @anon90963327,
You will need to have a rule(s) in the project you are moving the tasks to that reflect what you want the tasks to inherit.
So let’s say you have a custom field that has the options “inactive, ongoing, complete in the original project.” In the project you are sending tasks over to, you will create a rule that says:
Trigger: Tasks added to this project
Action: Change custom field to “ongoing.”
Does this make sense?
2 Likes
Welcome, @anon90963327,
To understand your question, it seems like you are asking why updating a task’s custom field(s) in one project does not show up when viewing the task in another project.
If that’s the case, it’s usually because you have not specified the custom field(s) to be global and are thus seeing separate, project-specific custom field(s) in each project instead of both projects sharing the same global field(s).
See this for more info:
Larry
3 Likes
I understand what we are going for here. The custom fields’ values however are a little more complicated and I couldn’t construct any relevant rules on the project.
Thank you for your suggestion anyway.
This is exactly what I’m looking for. I tried this method and it works. Thank you so much
1 Like
This topic was automatically closed after 6 days. New replies are no longer allowed.