rt-email-group-admin(8)
π rt-email-group-admin(8) β Request Tracker Reference π
okay bestie, gather round, because this is the command line tool for administrating NotifyGroup actions and it is literally the moment. it lives in the Request Tracker Reference manual (section 8, system administration, we love a grown-up section) and it is about to make your scrip game so much easier. β¨
πΈ NAME πΈ
rt-email-group-admin β the command line tool for administrating <rainbow>NotifyGroup</rainbow> actions. that's it, that's the whole job, and she does it flawlessly. π
π¦ SYNOPSIS π¦
rt-email-group-admin --list
rt-email-group-admin --create 'Notify foo team' --group Foo
rt-email-group-admin --create 'Notify foo team as comment' --comment --group Foo
rt-email-group-admin --create 'Notify group Foo and Bar' --group Foo --group Bar
rt-email-group-admin --create 'Notify user foo@bar.com' --user foo@bar.com
rt-email-group-admin --create 'Notify VIPs' --user vip1@bar.com
rt-email-group-admin --add 'Notify VIPs' --user vip2@bar.com --group vip1 --user vip3@foo.com
rt-email-group-admin --rename 'Notify VIPs' --newname 'Inform VIPs'
rt-email-group-admin --switch 'Notify VIPs'
rt-email-group-admin --delete 'Notify user foo@bar.com'
look at all those lil moves. pick one, run it, done. no notes. π
π DESCRIPTION π
so here's the tea π β this script will list, create, modify or delete scrip actions right there in the RT DB. once you've created an action, you can go ahead and use it in a scrip. that's the whole pipeline, bestie.
lowkey iconic demo of what this looks like in practice β you can create the following action using this script:
rt-email-group-admin --create 'Notify developers' --group 'Development Team'
and then boom, you add the following scrip to your Bugs queue:
Condition: On Create
Action: Notify developers
Template: Transaction
Stage: TransactionCreate
and just like that, your development team gets notified on every single new ticket in the queue. it's giving automatic. it's giving efficient. we're obsessed. ππ«Ά
β¨ USAGE β¨
rt-email-group-admin --COMMAND ARGS
that's it. that's the shape of every single invocation. command first, args after. periodt. π
π COMMANDS π
π list
Lists actions and its descriptions. your whole roster, laid out cute. π
π create NAME [--comment] [--group GNAME] [--user NAME-OR-EMAIL]
Creates new action with NAME and adds users and/or groups to its recipient list. Would be notify as comment if --comment specified. The user, if specified, will be auto-created if necessary. yes bestie, it just materializes them. no cap. β¨
π add NAME [--group GNAME] [--user NAME-OR-EMAIL]
Adds groups and/or users to recipients of the action NAME. The user, if specified, will be auto-created if necessary. same energy as create, just adding to the squad instead of building it from scratch. π«Ά
π delete NAME
Deletes action NAME if scrips doesn't use it.
β οΈ note the condition there β if a scrip is still using it, it's not going anywhere. she's protected. π
π§ switch NAME
Switch action NAME from notify as correspondence to comment and back. flip-flop, but make it functional. π¦
β rename NAME --newname NEWNAME
Renames action NAME to NEWNAME. glow-up for your action names, zero risk, iconic behaviour. π
π NOTES
If command has option --group or --user then you can use it more then once, if other is not specified.
(so like β stack up multiple --group flags, or multiple --user flags, as long as you're not mixing the two. iykyk. π)
πΈ AUTHOR πΈ
Ruslan U. Zakirov <ruz@bestpractical.com>
π¦ SEE ALSO π¦
RT::Action::NotifyGroup, RT::Action::NotifyGroupAsComment
and that's the whole page, bestie!! π this was documented with perl v5.40.1 and dated 2026-06-21, so if you're reading this you are officially up to date. go notify somebody. slay. πβ¨π
π¦ where this page comes from
- ubuntu stonking: request-tracker5 5.0.10+dfsg-3 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms