.TH "ti" "1" 
.SH "NAME" 
ti \(em issue tracking system built on Git 
.SH "SYNOPSIS" 
.PP 
\fBti\fR \fICOMMAND\fR [\fIARGUMENTS\fR]  
.SH "DESCRIPTION" 
.PP 
\fBti\fR, short for ticgit, is an issue tracker based 
on the Git revision control system.  It allows you to store bugs 
in your project in a separate \fBticgit\fP or 
\fBticgit-ng\fP branch of its development repository, 
thereby keeping open issues close to the source without cluttering 
the tree. 
 
.PP 
Every ticket consists of the following information: 
 
.IP "Title" 10 
A short summary of the problem.  This can be compared to the 
subject of an e-mail or to the first line of a Git commit 
message. 
 
.IP "Ticket ID" 10 
The Ticket ID (TicId) is the SHA-1 hash of the file which 
holds the ticket name (which is a normalized form of the 
title including the time of ticket creation and a small 
random number). It is used to uniquely identify a ticket. 
 
.IP "Number" 10 
Apart from TicIds, tickets can also be referred to by using 
their number.  This will often be preferred to TicIds when 
using ticgit from the command line (i.e., in everyday work), 
but ticket numbers are not persistent (they change with 
every \fBti list\fP invocation). 
 
.IP "" 10 
In the current version of ticgit, 
\fBti list\fP does not show numbers any more, 
but they can still be used (by counting manually). 
 
.IP "State" 10 
A ticket can either be \fBopen\fP, 
\fBresolved\fP, \fBinvalid\fP or put 
on \fBhold\fP. 
 
.IP "Assignment" 10 
The e-mail address of the person working on the ticket. 
 
.IP "Tag" 10 
A custom label which tells more about the nature of a ticket. 
A typical example is \fBfeature\fP (not a bug, 
but a feature suggestion). ticgit associates no special 
semantics to tags, you are free to choose them however you 
like. 
 
.IP "" 10 
Tickets can have an arbitrary number of tags. 
 
.IP "Points" 10 
You can use this integer value to assign some numerical 
value, such as a measure for the importance, to each ticket. 
Again, ticgit does not dictate how to use this field. 
 
.IP "Comments" 10 
Comments provide a simple form of communication between bug 
reporters and developers. 
 
.SH "COMMANDS" 
.PP 
\fBti\fR supports the following commands: 
.IP "\fBlist\fP" 10 
List tickets.  By default, only \fBopen\fP issues 
are shown; to show tickets in other states, use \fB-s 
STATE\fP.  You can also select by tag 
(\fB-t TAG\fP) or by assignment 
(\fB-a ADDRESS\fP).  When running 
\fBlist\fP, small integer numbers will be 
assigned to all shown tickets; you may use them to refer to 
tickets in other commands until you call 
\fBlist\fP again. 
 
.IP "\fBstate\fP" 10 
Pass a ticket ID and a state specification to set the 
ticket's state information.  You can omit the ticket ID to 
work on the current ticket. 
 
.IP "\fBshow\fP" 10 
Show everything known about the specified ticket.  You can 
omit the ticket ID to show the current ticket. 
 
.IP "\fBnew\fP" 10 
Create a new ticket.  This will launch an editor to let you 
enter a title, more detailled information about the issue, 
and some tags.  Initially, the ticket will be in the 
\fBopen\fP state. 
 
.IP "\fBcheckout\fP" 10 
Set the current ticket. 
 
.IP "\fBcomment\fP" 10 
Add a comment to the ticket specified on the command line. 
If you do not pass one, the current ticket will be used. 
 
.IP "\fBtag\fP" 10 
Pass a ticket ID and a tag name to add a label to an issue. 
You can omit the ticket ID to tag the current ticket.  If 
you use the \fB-d\fP option, the tag will be 
removed instead of added. 
 
.IP "\fBassign\fP" 10 
Assign the specified ticket to you (or to the given user, 
when \fB-u ADDRESS\fP is given).  If you omit 
the ticket ID, the current ticket will be assigned. 
Otherwise, you can prepend \fB-c\fP to the 
ticket ID to perform the \fBcheckout\fP operation 
after assigning the ticket. 
 
.IP "\fBpoints\fP" 10 
Pass a ticket ID and some integer to assign a point value to 
the given ticket.  If you only pass a number, this command 
manipulates the current ticket. 
 
.IP "\fBsync\fP" 10 
Synchronize tickets with the remote repository specified on 
the command line.  This uses the underlying push and pull 
command implemented in Git, so you can use your usual named 
remotes.  The default remote is \fBorigin\fP. 
 
.IP "\fBrecent\fP" 10 
Get a human-readable changelog of the tickets maintained by 
ticgit.  This command takes its information straight from 
the commit messages of the 
\fBticgit(\-ng)\fP branch. 
 
.PP 
These commands show usage information about themselves when passed 
the \fB\-\-help\fP option. 
 
.SH "FILES" 
.IP "\fB~/.ticgit/, ~/.ticgit-ng/\fP" 10 
The ticket cache. 
 
.SH "AUTHOR" 
.PP 
ticgit is Copyright \(co 2008 Scott Chacon 
<schacon@gmail.com>. 
 
.PP 
ticgit-ng is Copyright \(co 2011 Jeff Welling 
<jeff.welling@gmail.com>. 
 
.PP 
This manual page was written by Michael Schutte for the Debian 
GNU/Linux system (but may be used by others). 
 
.\" created by instant / docbook-to-man, Sun 01 Dec 2013, 10:56