> For the complete documentation index, see [llms.txt](https://docs.cubicl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubicl.io/task-and-project-management/projects/timeline-chart.md). # Timeline Chart You can use Timeline Chart to view the workload of members.
Each row represents a project member. The schedule displays all tasks assigned to that person. This way, you can see which days team members are busy or available. During task assignments, you can easily identify who is suitable. * You can apply **filters** in the Timeline. * You can view the schedule on a **daily** or **weekly** basis. * If there are leave entries added under **Time-Offs**, you can see them on the Timeline. * If you have the required permissions, you can update the schedule according to your **working days** and **hours** from the Settings button. Work Days and Hours on Timeline Chart --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cubicl.io/task-and-project-management/projects/timeline-chart.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.