NAME
ti — issue tracking system built on Git
SYNOPSIS
ti COMMAND [ARGUMENTS]
DESCRIPTION
ti, short for ticgit, is an issue tracker based in the Git revision
control system. It allows you to store bugs in your project in a
separate ticgit branch of its development repository, thereby keeping
open issues close to the source without cluttering the tree. Just like
any other branch, ticgit can be pushed to a public server and cloned by
everyone for inspection and local modification.
Every ticket consists of the following information:
Title 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.
Ticket ID 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.
Number 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
ti list invocation).
State A ticket can either be open, resolved, invalid or put on
hold.
Assignment
The e-mail address of the person working on the ticket.
Tag A custom label which tells more about the nature of a ticket.
A typical example is feature (not a bug, but a feature
suggestion). ticgit associates no special semantics to tags,
you are free to choose them however you like.
Tickets can have an arbitrary number of tags.
COMMANDS
ti supports the following commands:
list List tickets. By default, only open issues are shown; to
show tickets in other states, use -s STATE. You can also
select by tag (-t TAG) or by assignment (-a ADDRESS). When
running list, small integer numbers will be assigned to all
shown tickets; you may use them to refer to tickets in other
commands until you call list again.
state 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.
show Show everything known about the specified ticket. You can
omit the ticket ID to show the current ticket.
new 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 open
state.
checkout Set the current ticket.
comment Add a comment to the ticket specified on the command line.
If you do not pass one, the current ticket will be used.
tag 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 -d option, the tag will be removed instead of added.
assign Assign the specified ticket to you (or to the given user,
when -u ADDRESS is given). If you omit the ticket ID, the
current ticket will be assigned. Otherwise, you can prepend
-c to the ticket ID to perform the checkout operation after
assigning the ticket.
These commands, except for state, show and checkout, show usage
information about themselves when passed the -h option.
FILES
~/.ticgit/
The ticket cache.
AUTHOR
ticgit is Copyright © 2008 Scott Chacon <schacon@gmail.com>.
This manual page was written by Michael Schutte for the Debian
GNU/Linux system (but may be used by others).
ti(1)