> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/tickets/timeline-und-arbeitsprotokoll.md).
# Timeline and work log
## Timeline
The timeline displays ticket and task events by user and calendar week.
Timeline in Ticket Management
Enable in the ticket list **Timeline \[D]** or open the tab **Tasks** of a ticket.
## Work log
Work log
Item
Title
Description
[C]
Work log
Opens the chronological change history of the ticket.
[F]
Back
Returns to the previous view.
The work log lists chronologically:
* creation and updates of the ticket,
* creation and assignment of tasks,
* status changes of tickets and tasks,
* the user performing the action and the time of the change.
Using linked ticket and task numbers, you can go directly to the respective entry.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/tickets/timeline-und-arbeitsprotokoll.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
