When using the feature “convert task to project”, 9 out of 10 times, we want to multi-home that task into the created project so that we have a reference point of the original submission. This feature is often used when using a Form submission as project intake and then converting the task into a project, because the request has been approved to be launched into a full project.
I know that the task information is available on the Overview tab, but nothing beats having the task itself in the project as a reference to the original.
Can there be an option (or can it be automatic) to always multi-home the task into the newly created project that’s created from that task?
I would certainly advocate this being an option in the rule action but not automatically added to the newly created project. I have client use cases where the form submission would contain sensitive data (eg. budgets, rates etc) that not all project members should be privy to.
Is there a way to get an update on if this feature will be considered? I’m not sure how the voting system works but our team would definitely implement this - we’re manually doing it right now.
Is there a workaround for this? I came here searching for a way to get the form information added to a specific task in the project after conversion, but multi-homing the task to that project would work just as well.
If not, is there a way to get the information from the task that creates the project into a specific task inside the project, rather than or in addition to the overview tab?
In both cases, you could manually multi-home the task in question into the new project so it would be seen there as well.
If helpful, you could include that setup step in the project template the new project is based on (if you use one) as a reminder; not automation, but at least it will be an automatic reminder.
