1 1 <h1>Fossil Cookbook</h1>
2 2 The <cite>Fossil</cite> Cookbook is a collection of task-oriented instructions for intermediate users who wish to do more than basic operations with their <cite>Fossil</cite> repositories. The [Tutorial|tutorial] is a more suitable place for newcomers trying to learn the basic concepts to go first before tackling these recipes.
3 3
4 4 <h2>Index</h2>
5 5 <ul>
6 - <li> Server recipes:
6 + <li>Server recipes:
7 7 <ul>
8 - <li> <a href="#CGI">Using <cite>Fossil</cite>'s Built-In CGI</a>
8 + <li><a href="#CGI">Using <cite>Fossil</cite>'s Built-In CGI</a>
9 9 </ul>
10 - <li> <a href="#env">Using Environment variables</a>
11 - <li> <a href="#css">Example CSS</a>
12 - <li> <a href="#source-hilight">Source highlighting</a>
13 - <li> <a href="#win32dev">Fossil Win32 Development Machine setup</a>
14 - <li> <a href="#wysiwig">Javascript HTML WYSIWYG editor control</a>
10 + </li>
11 + <li><a href="#env">Using Environment variables</a></li>
12 + <li><a href="#css">Example CSS</a></li>
13 + <li><a href="#source-hilight">Source highlighting</a></li>
14 + <li><a href="#win32dev">Fossil Win32 Development Machine setup</a></li>
15 + <li><a href="#wysiwig">Javascript HTML WYSIWYG editor control</a>
15 16 <ul>
16 - <li> <a href="#tinymce">TinyMCE</a>
17 - <li> <a href="#markitup">markitup!</a>
17 + <li><a href="#tinymce">TinyMCE</a></li>
18 + <li><a href="#markitup">markitup!</a></li>
18 19 </ul>
20 + </li>
21 + <li><a href="#ticket-checkin-links">Link tickets to checkins</a></li>
19 22 </ul>
20 23
21 24 <h2><a name="CGI">Using <cite>Fossil</cite>'s Built-In CGI</a></h2>
22 25 <h3>Motivation</h3>
23 26 * You want to share a repository through your existing web infrastructure.
24 27 * You want to share more than one repository at the same time.
25 28
................................................................................
659 662 $(document).ready(function() {
660 663 $("#" + n).markItUp(mySettings);
661 664 });
662 665 }
663 666 }
664 667 </script>
665 668 </pre>
669 +
670 +<h2><a name="ticket-checkin-links">Linking Tickets to Checkin's</a></h2>
671 +
672 +It's easy to link a checkin to a ticket... simply include <nowiki>[ticket-uuid]</nowiki> in your commit comment. Now, when you do that, you also have the ability to link a ticket to the associated checkin(s).
673 +
674 +This is just one way of doing this, and what I decided to do. You can of course alter it for your own style/layout.
675 +
676 +First: Add a "Short UUID" to your View Ticket page. You can do this by:
677 +
678 +<verbatim>
679 +<th1>
680 +set shortUuid [string range $tkt_uuid 0 9]
681 +</th1>
682 +</verbatim>
683 +
684 +Then, display that to the user somewhere:
685 +
686 +<verbatim>
687 +Uuid: $<shortUuid>
688 +</verbatim>
689 +
690 +All that does is make it easy for the developer to copy/paste a sensible UUID into their commit log.
691 +
692 +Now, continuing, on the same View Page add a link to view associated tickets:
693 +
694 +<verbatim>
695 +<a href="/timeline?y=ci&s=$<shortUuid>">associated tickets</a>
696 +</verbatim>
697 +
698 +What this does is searches all checkin's for the tickets uuid, thus, you can now see all checkin's that are linked with the given ticket.