+++ /dev/null
-
-Things the cli must do
- create ticket
- comment
- reply
- update ticket metadata
- search for tickets
- update a bunch of tickets.
- list tickets
- login/logout
-
-
-should support multiple rt servers
-
-create/edit/update should use EDITOR or take from a file or stdin
-
-should be able to update ticket sttributes from a commandline without invoking an editor or needing to use stdin.
-
-login/logout should store RT session cookies rather than constantly transmitting the username/password combo.
-
-rtserver and rt username should come from env variables. but should be able to be overridden by commandline options.
-
-rt password should be able to be specified on the commandline (say from a script) or, failing that be prompted for within the application (as rt's sbin/initdb script does) ...or maybe able to be read from a stash file on disk.
-
-must be able to dowaload attachments from cli.
-
- it might also be cool to be able to generate session-length urls for attavhments so you can use a browser. but that's not necessary.
-
-
-I'm envisioning this as similar to the subversion cli, actually.
-