| [1026] | 1 | RT TRICKS |
|---|
| 2 | |
|---|
| 3 | To edit stuff like ticket status, click "Basic" in the left. |
|---|
| 4 | |
|---|
| 5 | Note the multiple ways to search for tickets: you can click "All |
|---|
| 6 | {new,open,waiting} Scripts Tickets" on the home page in the center, or |
|---|
| 7 | "Scripts" on the right in the list of queues. |
|---|
| 8 | |
|---|
| 9 | You should take a look in "Preferences" at the left. Make sure "Notify |
|---|
| 10 | yourself of own updates" is on. You can also set the "Default Working Queue" |
|---|
| 11 | to Scripts, and give yourself a signature referring to scripts@mit.edu. |
|---|
| 12 | |
|---|
| [1366] | 13 | Another useful option here is to set a password, so you don't need certs to log |
|---|
| 14 | in (and so you can use the zephyrbot). The zephyrbot will take commands to -c |
|---|
| 15 | scripts -i [ticket number] of the form /set status=resolved or /set |
|---|
| 16 | owner=geofft. You need to drop a file in /mit/geofft/web_scripts/rt/rt-passwords |
|---|
| 17 | by your username with the format: |
|---|
| [1026] | 18 | |
|---|
| [1366] | 19 | "username" "yourawesomepassword" |
|---|
| 20 | |
|---|
| 21 | And then ask geofft (zwrite geofft) to restart the RT bot. |
|---|
| 22 | |
|---|
| [1026] | 23 | You can also place these commands on a line by themselves inside e-mail; they |
|---|
| 24 | will be acted upon and removed before the e-mail gets sent back out. |
|---|
| 25 | |
|---|
| 26 | Don't use the To field, it doesn't work. If you want to send the ticket somewhere else, use CC. |
|---|
| 27 | |
|---|
| 28 | Don't CC other RT queues, it doesn't work. If you really need to, use your |
|---|
| 29 | e-mail client to forward it and remove the [help.mit.edu #nnn] tag. |
|---|
| 30 | |
|---|
| 31 | E-mail to scripts-comment that carries a [help.mit.edu #nnn] tag will be |
|---|
| 32 | included in the ticket history for the scripts team to see, but will not be |
|---|
| 33 | sent to the user. You can use this for asking "Help, what do I do here?" |
|---|
