FYI here is the documentation on multi-homing:
There are actually a lot of good use cases for multi-homing tasks; you can search the forum here for “multi-hom” and find discussions about this topic. Here are a few:
Hi and welcome, @Monique_Lay ,
One approach would be to adopt a standard of including one “reference” task in every project that you want to keep track of.
For all such reference tasks, make the task title be a short phrase describing the project. “Multi-home” (add the task to another project as well as the one project it’s already in) the task to a project called “Projects Summary” (you will need to first create this project so you can multi-home into it; I like List projects though you could …
Unfortunately visibility is set at the Project-level (vs. Task-Level), so I don’t think it’s possible accomplish exactly what you’re looking for.
That said, could you create 2 separate projects (1 for internal work, 1 for client work) and multi-home Employee tasks from their Internal Project to the Client Project? That way, whatever is multi-homed to the Client Project is visible to the client, but you don’t need to give them access to the Employee Project with presumably a lot more tasks.
It would be great for companies in a KanBan framework to allow a task to belong to multiple projects, since one task might as well belong to the Development Project and to a Client Project. It would increase flexibility.
If you have access to Portfolios, you can see the new timeline per project but this is only on project level.
The other option to see all tasks on a timeline is to create a project called “Overview” or “All tasks” and then multi-home all the tasks in this project that will act as a overview on the calendar and timeline view.
This could be a bit overwhelming, i would maybe do this with certain milestones only.
3 Likes