NAME
rtpaste - see your tickets from the command line
DESCRIPTION
Let's you pipe commands to and from request tracker tickets (http://bestpractical.com/rt/)
This is more designed for colaborative programming, but there is no reason you could not use it as part of some bigger automation
USAGE
rtpaste [COMMAND] optionsCOMMANDS
setup - tell me your rt password
A good place to start if you've not used rtpaste before
You will be asked to do setup automatically if you have not already, you just need to provide the url, username and password for request tracker
ticket <id>
show the current status of a the ticket who's id is passed as the only argument
search <query-name>
Show the results of pre-defined rt ticket searches.
These are specified either directly in the script, or in your .rc file
without arguments, you'll be shown a list of searches
put
an alias of ...
create --queue=QueueName --subject=some stuff [--message=stuff] < file
creates a ticket in RT, takes
--queue=QueueName the name of the queue to create the ticket in
--subject=some stuff the subject line for your ticket
Ideally you'd start this with [patch] becasue you're being super helpful and submitting fixes for the stuff you're having trouble with
optionally --message=stuff the body of the ticket
if you don't specify this, the ticket body will be read from STDIN
get <id>
retreive the contents of the transaction that create the ticket who's id you pass
(will make some attempt to get an id from a url)
FILES/ENVIRONMENT
~/.rtpaste.rc
you can also set $RTPASTE_RC in your environment to point to a config file instead
internally the script's name ($0) is used to determine both the name for the rc file and the environment variable used to override it...
symlink trickery
for example:
ln -s mycorp-tickets rtpaste... will lead to mycorp-tickets checking for ~/.mycorp-tickets.rc and looking for MYCORP-TICKETS_RC in the environment
This is the least pesky way I could think of to use many differing RT's as the same user, this can be done in your own ~/bin (as long as it's in $PATH) or globally by root...
There is no global config file, although you can replace $DEFAULT_RT in the script ...