Timeline vs assigned tasks

In our actual Asana projects, we have had a lot of success with separating out Timeline from assigned tasks. The timeline represents phases of a project in a waterfall method with dependencies built in. The tasks are smaller portions of each thing we or the client needs to get done.

The client portal doesn’t allow us to hold to this in a way that would make sense. It would be much bettter if we could filter the Timeline based on custom task type (which others have suggested) in the portal but ALSO if the task list in the portal could be filtered to only show things we actually need clients to DO. Without that separation, we can basically either use the timeline or use the client task list, but we cannot effectively use both.

I know not all teams separate these tasks with a custom task type like we do, but I would bet that many want a client-facing timeline to be able to show the work that their team is doing and the work that a client will ned to do without having all their internal tasks show up in the client’s task list.

1 Like

Hi @Abby_Hayes,
I agree with this. There’s an important difference between a client-facing timeline and client-action tasks. The timeline should show phases, milestones, and dependencies, while the portal task list should ideally show only items the client needs to act on. Without filtering, teams either expose too much internal detail or lose the ability to use both views effectively. Portal-level filters based on custom fields/task type — especially something like Client action required — would make the Client Portal much more usable for teams that manage detailed internal work and client-facing deliverables in the same project. Thank you for this.