Changeset 2487 for branches/fc19-dev/locker/doc/tickets/rt.txt
- Timestamp:
- Nov 15, 2013, 11:35:17 PM (11 years ago)
- Location:
- branches/fc19-dev
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/fc19-dev
- Property svn:mergeinfo changed
/trunk merged: 2440-2442,2444-2453,2456-2461,2463-2468,2470-2478,2480-2485
- Property svn:mergeinfo changed
-
branches/fc19-dev/locker
- Property svn:mergeinfo changed
/trunk/locker (added) merged: 2441-2442,2464-2465
- Property svn:mergeinfo changed
-
branches/fc19-dev/locker/doc/tickets/rt.txt
r1369 r2487 8 8 9 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. 10 yourself of own updates" is on. You can also set the "Default Working 11 Queue" to Scripts, and give yourself a signature referring to 12 scripts@mit.edu. 12 13 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: 14 Another useful option here is to set an RT password for your account, 15 so you don't need certs to log in (though it sometimes will keep 16 asking you for your password on each page load if you don't have 17 certs) and so you can use the BarnOwl RT module or the zephyrbot. 18 The BarnOwl RT module is the preferred option. To install it, run 20 19 21 "username" "yourawesomepassword" 20 mkdir -p ~/.owl/modules 21 cd ~/.owl/modules 22 ln -s /mit/snippets/rt/BarnOwl RT 22 23 23 And then ask geofft (zwrite geofft) to restart the RT bot. 24 Then in BarnOwl run ":reload-module RT". The RT module adds the :rt 25 command to barnowl. Run ":rt help" for more information; useful 26 shortcuts are ":rt r" to set the status to resolved and ":rt d" to set 27 the status to deleted. The zephyrbot will take commands to -c scripts 28 -i [ticket number] of the form /set status=resolved or /set 29 owner=geofft. Talk to ezyang to be added to the zephyrbot. 24 30 25 Note that in the event that Geoff's account is compromised, it is possible26 for an attacker to use this password do manipulate tickets in *any* 27 queue you have bits on, not just the Scripts one.31 Note that in the event that Edward's account is compromised, it is 32 possible for an attacker to use this password do manipulate tickets in 33 *any* queue you have bits on, not just the Scripts one. 28 34 29 The RT bot will post ticket notifications as -c scripts -i nnn. If you are30 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.35 The RT bot will post ticket notifications as -c scripts -i nnn. If 36 you are responding to a ticket, it is conventional to post "lock" to 37 the appropriate instance, so others know not to pre-empt you. You 38 should post "unlock" once you are done handling the ticket. 33 39 34 You can also place these commands on a line by themselves inside e-mail; they 35 will be acted upon and removed before the e-mail gets sent back out. 40 You can also place these commands on a line by themselves inside 41 e-mail; they will be acted upon and removed before the e-mail gets 42 sent back out. 36 43 37 If you're adding a *comment* (such as when you're forwarding a cname request38 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 use42 the 'To:' field.44 If you're adding a *comment* (such as when you're forwarding a cname 45 request on to IS&T), don't use the 'To:' field, because it'll be 46 clobbered by our RT scrips and the mail won't actually go to the 47 destination you added. Instead, you should use the 'Cc:' field. 48 Similarly, if you're adding *correspondence*, the 'Cc:' field will be 49 clobbered and you need to use the 'To:' field. 43 50 44 Don't CC other RT queues, it doesn't work. If you really need to, use your 45 e-mail client to forward it and remove the [help.mit.edu #nnn] tag. 51 Don't CC other RT queues, it doesn't work. If you really need to, use 52 your e-mail client to forward it and remove the [help.mit.edu #nnn] 53 tag. 46 54 47 E-mail to scripts-comment that carries a [help.mit.edu #nnn] tag will be 48 included in the ticket history for the scripts team to see, but will not be 49 sent to the user. You can use this for asking "Help, what do I do here?" 55 E-mail to scripts-comment that carries a [help.mit.edu #nnn] tag will 56 be included in the ticket history for the scripts team to see, but 57 will not be sent to the user. You can use this for asking "Help, what 58 do I do here?"
Note: See TracChangeset
for help on using the changeset viewer.