# Logging on a separate ticket (/en/docs/usage/timer-log-separate-ticket)









Sometimes you work on a specific ticket but must log the time onto a **different ticket** (a billing ticket, a parent ticket, a team ticket…). Clepsydre lets you decouple the **tracked ticket** from the **logging ticket**.

<Callout type="info">
  This feature depends on the setting **Settings > Time Tracking > Allow logging on a different ticket**.
  If this setting is disabled, the **Log on** section is hidden and time is always logged on the active ticket.
</Callout>

## The "Log on" panel [#the-log-on-panel]

On the active ticket, the &#x2A;*"Log on"** panel lets you choose a different logging ticket.

1. First select the ticket you are working on as usual (active ticket).
2. In **Log on*&#x2A;, click the edit icon to open &#x2A;*"Choose logging ticket"**.
3. Search for and select the destination ticket.

The timer **stays on the active ticket**, but the time will be logged onto the chosen ticket.

<div align="center">
  <img alt="Log on panel" src="__img0" />
</div>

<Callout type="info">
  To go back to the classic behavior, click **Use active ticket**: time will be logged onto the tracked ticket again.
</Callout>

## The comment is completed automatically [#the-comment-is-completed-automatically]

This is the key part of the feature. When the logging ticket differs from the tracked ticket, Clepsydre **automatically prefixes the comment** with a first line recalling the ticket you actually worked on:

```
#1234 - Current ticket subject
```

This way, even if the time is logged elsewhere, the trace of the original ticket stays visible in the time entry comment. The prefix is handled automatically:

* it is **added** when you log onto a different ticket;
* it is **updated** if you change the tracked ticket;
* it is **hidden** in the timeline and history UI to keep things readable.

<div align="center">
  <img alt="Context comment" src="__img1" />
</div>

## Display in the timeline [#display-in-the-timeline]

In the [timeline](/en/docs/usage/timer-timeline&#x29;, an entry logged onto another ticket shows a note like &#x2A;*"Logged on #ID · Ticket"**, so you can spot cross-ticket logging at a glance.

<div align="center">
  <img alt="Timeline with context comment" src="__img2" />
</div>

## Memory [#memory]

When you re-select a previously tracked ticket, Clepsydre **restores the last logging ticket** used for it, based on the timeline history. You therefore don't have to reconfigure logging every time.