Report Listing

Ticket View

List of Reports

Get a list of all the available reports with:

$ cm reports

System Properties

This will dump on screen all the Milestones, Components, Versions:

$ cm properties

Creating a ticket

Creating a ticket will work similarly to writing a new email in mutt, it loads
your current $EDITOR and lets you edit the details of the ticket. Assuming
all the parameters are correct, it will create the ticket as soon as you save
and exit and return the ticket number. If your ticket does not appear valid
(missing required field, inexistent Milestone, etc.) cartman will stop and
lists each error and let you return to your editor:

The first parameter to cm is the owner of the ticket, it populates the
To field by default:

$ cm new jcarmack

If your Trac has custom fields, you can use their identifier in the headers,
e.g.:

story_id: 5123
iteration: 15

If you specify a template with -t, cartman will look for a matching file in the
~/.cartman/templates folder and will use it as a base for your ticket:

$ cm new -t sysadmin

Commenting on a ticket

Just like creating a ticket, adding a comment is just like mutt, your current
$EDITOR will be loaded on a blank file for you to edit. Upon save and exit,
cartman will commit this new comment and return silently, unless an error
occurs:

$ cm comment 1

If the comment is short enough to fit on the command line, you may use the
-m flag as such:

$ cm comment 1 -m "you forgot to call twiddle()"

View/Set the status of a ticket

View the current status of a ticket, and the available statuses:

$ cm status 1

Set a ticket as accepted:

$ cm status 1 accept

If you need to add a comment with this status change, you can use the -c
flag, it will open your default editor:

$ cm status 1 reopen -c

You may also use the -m flag to define the comment in-line, without the use
of an editor:

$ cm status 1 reopen -m "does not work with x = y"

Advanced configuration

If you are using vim as your default editor, you also might want to add
email-like syntax highlighting to match the .cm.ticket extension:

autocmd BufNewFile *.cm.ticket setf mail

If you use multiple Trac sites, you can have multiple configurations in the
same file using the section to separate the sites, here is an example: