Changeset 1414 for branches/locker-dev/locker/doc/tickets/rt.txt
- Timestamp:
- Jan 12, 2010, 11:55:27 PM (15 years ago)
- Location:
- branches/locker-dev/locker
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/locker-dev/locker
-
Property
svn:mergeinfo
set to
False
/trunk/locker merged eligible
-
Property
svn:mergeinfo
set to
False
-
branches/locker-dev/locker/doc/tickets/rt.txt
r1026 r1414 10 10 yourself of own updates" is on. You can also set the "Default Working Queue" 11 11 to Scripts, and give yourself a signature referring to scripts@mit.edu. 12 Another useful option here is to set a password, so you don't need certs to13 log in (and so you can use the zephyrbot).14 12 15 The zephyrbot (currently down) will take commands to -c scripts -i [ticket 16 number] of the form /set status=resolved or /set owner=geofft. 13 Another useful option here is to set an RT passwordfor your account, so you 14 don't need certs to log in (though it sometimes will keep asking you for 15 your password on each page load if you don't have certs) and so you can use 16 the zephyrbot). The zephyrbot will take commands to 17 -c scripts -i [ticket number] of the form /set status=resolved or 18 /set owner=geofft. You need to drop a file in 19 /mit/geofft/web_scripts/rt/rt-passwords by your username with the format: 20 21 "username" "yourawesomepassword" 22 23 And then ask geofft (zwrite geofft) to restart the RT bot. 24 25 Note that in the event that Geoff's account is compromised, it is possible 26 for an attacker to use this password do manipulate tickets in *any* 27 queue you have bits on, not just the Scripts one. 28 29 The RT bot will post ticket notifications as -c scripts -i nnn. If you are 30 responding to a ticket, it is conventional to post "lock" to the appropriate 31 instance, so others know not to pre-empt you. You should post "unlock" once 32 you are done handling the ticket. 17 33 18 34 You can also place these commands on a line by themselves inside e-mail; they 19 35 will be acted upon and removed before the e-mail gets sent back out. 20 36 21 Don't use the To field, it doesn't work. If you want to send the ticket somewhere else, use CC. 37 If you're adding a *comment* (such as when you're forwarding a cname request 38 on to IS&T), don't use the 'To:' field, because it'll be clobbered by our 39 RT scrips and the mail won't actually go to the destination you added. 40 Instead, you should use the 'Cc:' field. Similarly, if you're adding 41 *correspondence*, the 'Cc:' field will be clobbered and you need to use 42 the 'To:' field. 22 43 23 44 Don't CC other RT queues, it doesn't work. If you really need to, use your
Note: See TracChangeset
for help on using the changeset viewer.