Hi,
I found some issue when ‘Convert task to project’, and connect to a portfolio. We have set up same customized fields for the task, for the project it converted to, and for the portfolio it’s connected to.
However, the field value only syncs between task and portfolio, but not with project. This to me is wierd, as after converting task project we will only work with the project and make updates there, but if the updates won’t be populated to portfolio do we always need to manually update in the portoflio???
Anyone has a solution for that?
BR,
Bei
Let me sum p what is currently expected:
- a task has fields and values
- you convert the task to a project and place it into a portfolio
- if the portfolio has the same fields, then the project will show the values the task had
What is NOT expected, and is not a bug:
- if you then change values on the task, the project values won’t change
I feel like you expected it to work isn’t it?
Hi Bastien,
You got it right, the task fields does accumulated into the portfolio correctly, but it doesn’t populate to the project it converted to, when ‘covert task to project’ I chose to convert based on template, and in the template the same fields as for the task are facilitated. But the field values for the tasks doesn’t shows up on the project it converted to, which is strange to me.
I experienced this exact same issue and looking for a solution!
1 Like
That’s expected behaviour at this stage I am afraid.
Hi Bastien,
That’s pity… Do you know if there’s plan from Asana to develop the function?
Not that I know of. If I understood what you need correctly, for me it doesn’t make sense in most cases I saw. You define values on a task so it can then be attached to the project object. There are many cases where you don’t want all the new tasks to inherit the values. Asana could potentially offer the option through a toggle, but usually they try to stay light in terms of configuration. We’ll see.