You end up with a nice (automatic) trace of all changes pertinent to the ticket (if the developers have the discipline to always provide the ticket reference).

This is particularly appealing in fossil since it comes with the ticketing embedded.

In fact, many organizations adopt the rule - no check-ins without a ticket. Perhaps this could be a fossil option.

Note: it is possible for a check-in to apply to multiple tickets

jeremy_c added on 2009-12-31 04:07:10:
You can now do this in a round-about way... What I did:

First: Add a "Short UUID" to your View Ticket page. You can do this by:

<th1>
set shortUuid [string range $tkt_uuid 0 9]
</th1>

Then, display that to the user somewhere:

Uuid: $<shortUuid>

All that does is make it easy for the developer to copy/paste a sensible UUID into their commit log.

Now, continuing, on the same View Page add a link to view associated tickets:

<a href="/timeline?y=ci&s=$<shortUuid>">associated tickets</a>

What this does is searches all checkin's for the tickets uuid.

I've also added this to the Cookbook page.