Re: [rt-users] Hiding Reminder Section? Also Watchers, Approval?
Hi Christopher, have a look at share/html/Elements/Tabs. In this file you will find the entries for the main menu and links to the sub menus. Copy the file to your local directory and modify it there, e.g. delete the part with the Approvals (I did the same here). But I bet you will figure out how it works once you have a look at the file. Best regards, Ben Christopher Short wrote: > > Hi there, > > I'm currently setting up rights for the main users of of our RT > installation. > > On a run-through with one of them, they were confused and distracted > by several sections which we won't be using but are featured rather > prominently on the site. > > These were: > > * the "Reminder" section on Tickets > > * the "New Watchers" section on the "People" tab of a > Ticket > > * The "Approval" link on the menu bar. > > > > I'm hoping hiding these sections are as easy as removing certain > rights for those user groups, especially as we'd probably still like > the sysadmin to have the ability to add Watchers. Note that these > ordinary users don't have the Watch or WatchAsAdminCC rights, so it > seems strange that they can add Watchers (even themselves). > > > > I dread hearing that the only answer is hiding those sections with CSS. > > > > Christopher > > > > ___ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: > > If you sign up for a new RT support contract before December 31, we'll take > up to 20 percent off the price. This sale won't last long, so get in touch > today. > Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. > > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Procmail filtering
Have you tried queue\ with\ spaces? Keep up with me and what I'm up to: http://theillien.blogspot.com John Arends wrote: > I'm trying to use procmail to filter messages coming into RT but I can't > figure out how to pass a queue name to my procmail recipe if it has > spaces in it. > > QUEUE=\"queue with spaces\" and QUEUE='queue with spaces' both cause > failure. > > Any suggestions? > > My /etc/aliases looks like this: > > rt-general: "|/etc/smrsh/procmail -m QUEUE=General > /etc/procmail/rt-deliver.rc" > > rt-deliver.rc looks like this: > > # Trash Outlook autoreplies > :0 w > * ^subject:.*Out of Office AutoReply > /dev/null > > #Strip Attachments and HTML > :0 fw >|/usr/local/bin/stripmime.pl > > #Send it on to the RT queue > :0 w > | /usr/sbin/rt-mailgate --queue $QUEUE --action correspond --url > https://myserver.edu/rt/ > > ___ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: > > If you sign up for a new RT support contract before December 31, we'll take > up to 20 percent off the price. This sale won't last long, so get in > touch today.Email us at [EMAIL PROTECTED] or call us at +1 617 > 812 0745. > > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy > a copy at http://rtbook.bestpractical.com > ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Page Break problems in printing Tickets (version 3.6.4)
Hi, When we try printing a displayed ticket longer than a page, the box that happens to be at the bottom of the printed page is garbled (missing lines, last line shown only half etc.) and also next page is missing content. Depending on the content of the ticket, the last box on the page is either the "Custom Fields" or the "History" section, and they behave the same. Also, this happens both with IE6 and Firefox as the browser. Does somebody have some hint if changing any settings, e.g. in the html/NoAuth/css/print.css stylesheet, helps to have a clean page break in these sections? Thanks a lot in advance, Gabriele Franzini Nerviano Medical Sciences SRL Nerviano Italy ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Shredder no_tickets Users option behaviour
I've set the arguments for the RTx-Shredder Users plugin to limit: 100 status: any name: email: replace_relations: Nobody no_tickets: true This pulled up a list of users that consist of both valid users and those created from incoming spam. I then set the no_tickets to false and got the same list. Why is there no difference? -- Keep up with me and what I'm up to: http://theillien.blogspot.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Shredder no_tickets Users option behaviour
And to clarify, I know that the status of any will pull up any user regardless of privileges but the users that come up which are enabled do have tickets with which they are associated. Keep up with me and what I'm up to: http://theillien.blogspot.com Mathew Snyder wrote: > I've set the arguments for the RTx-Shredder Users plugin to > limit: 100 > status: any > name: > email: > replace_relations: Nobody > no_tickets: true > > This pulled up a list of users that consist of both valid users and those > created from incoming spam. I then set the no_tickets to false and got the > same > list. Why is there no difference? > ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Apache MPM ?
I have never used it in production using worker, but I have done development deployments that seemed to work fine. YMMV. M On Mon, 2007-11-12 at 17:47 -0500, [EMAIL PROTECTED] wrote: > Does RT work properly with apache's worker thread implementation ? I > would assume it is okay since I have only ever heard of problems with > php code in on the worker model. > > Any feedback or tips/tweaks or the like are appreciated. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Procmail filtering
"$QUEUE" in my .rc file fixed the problem. It's quite obvious why that is the solution now, but when banging your head against the wall for an hour you sometimes don't see it. Mathew Snyder wrote: Have you tried queue\ with\ spaces? Keep up with me and what I'm up to: http://theillien.blogspot.com John Arends wrote: I'm trying to use procmail to filter messages coming into RT but I can't figure out how to pass a queue name to my procmail recipe if it has spaces in it. QUEUE=\"queue with spaces\" and QUEUE='queue with spaces' both cause failure. Any suggestions? My /etc/aliases looks like this: rt-general: "|/etc/smrsh/procmail -m QUEUE=General /etc/procmail/rt-deliver.rc" rt-deliver.rc looks like this: # Trash Outlook autoreplies :0 w * ^subject:.*Out of Office AutoReply /dev/null #Strip Attachments and HTML :0 fw |/usr/local/bin/stripmime.pl #Send it on to the RT queue :0 w | /usr/sbin/rt-mailgate --queue $QUEUE --action correspond --url https://myserver.edu/rt/ ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today.Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Asset Tracker - change the status titles
In our situation, some of the default statuses of an Asset are either "duplicates" or unused. For example; test and development would mean the same thing to us, and we have no clue what a status of dr would be :-) ) I found in the source the following: # You can define new statuses and even reorder existing statuses here. # WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT # will break horribly. @ActiveStatus = qw(production development qa dr pilot test) unless @ActiveStatus; @InactiveStatus = qw(retired) unless @InactiveStatus; 1) I was wondering if the "DO NOT DELETE" would break AT ? (since the piece seems to be a copy/paste of RT_Config.pm) 2) Does changing = delete ? For example could we change "pilot" to "storage" or would we just have to add a new Status to get "storage" Our main goal is to have a status field for: a) in production - i.e. out in the field being used b) in repair - was in production, but has come back in to be fixed c) ready to go - is sitting somewhere, ready to go into production at any time. d) development and qa are OK as is for us. of course, the current production status works for A above, but we are trying to figure out what to do for B and C. -- http://gentgeen.homelinux.org # Associate yourself with men of good quality if you esteem your own reputation; for 'tis better to be alone then in bad company.- George Washington, Rules of Civility ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Prevent changing of Custom Field
To all, I have a Custom Field that has two values, "Yes" and "No". I have granted "ModifyCustomField" to a certain group. When someone of that group modifies that CF, I want to "disallow" or "stop" that update from occuring if the ticket owner is the same person modifying the CF. Is that really possible? I've been assuming that when a custom condition checked the "NewValue", the "NewValue" was already a fact, set in stone. Is my assumption correct? If so, I could create a scrip to undo the change, but that seems a bit bulky and I would prefer to stop the change before it is completed. Any help??? Thanks. Kenn LBNL ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Asset Tracker - change the status titles
On 11/14/07, Kevin Squire <[EMAIL PROTECTED]> wrote: > In our situation, some of the default statuses of an Asset are either > "duplicates" or unused. For example; test and development would mean > the same thing to us, and we have no clue what a status of dr would be > :-) ) > > I found in the source the following: > # You can define new statuses and even reorder existing statuses here. > # WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT > # will break horribly. > > @ActiveStatus = qw(production development qa dr pilot test) unless > @ActiveStatus; > @InactiveStatus = qw(retired) unless @InactiveStatus; > > 1) I was wondering if the "DO NOT DELETE" would break AT ? (since the >piece seems to be a copy/paste of RT_Config.pm) > It probably won't break AT. You might want to grep for those statuses in the code to be sure. > 2) Does changing = delete ? For example could we change "pilot" >to "storage" or would we just have to add a new Status to get >"storage" > You probably can remove pilot and add storage. -Todd > Our main goal is to have a status field for: > a) in production - i.e. out in the field being used > b) in repair - was in production, but has come back in to be fixed > c) ready to go - is sitting somewhere, ready to go into production at >any time. > d) development and qa are OK as is for us. > > of course, the current production status works for A above, but we are > trying to figure out what to do for B and C. > > -- > http://gentgeen.homelinux.org > > # > Associate yourself with men of good quality if you esteem > your own reputation; for 'tis better to be alone then in bad > company.- George Washington, Rules of Civility > ___ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: > > If you sign up for a new RT support contract before December 31, we'll take > up to 20 percent off the price. This sale won't last long, so get in touch > today. > Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. > > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] Hiding Reminder Section? Also Watchers, Approval?
Thanks, I'll give that a go. I've also discovered that anyone with the ModifyTicket right can add watchers - the Watch and WatchAsAdminCC rights are only useful for people who don't have ModifyTicket. I assume this means there's no way I can turn off "Add Watchers" for people who have ModifyTicket. I still hope to find a way to hide or remove Reminders. Christopher -Original Message- From: Benjamin Weser [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 14, 2007 8:16 PM To: Christopher Short Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Hiding Reminder Section? Also Watchers, Approval? Hi Christopher, have a look at share/html/Elements/Tabs. In this file you will find the entries for the main menu and links to the sub menus. Copy the file to your local directory and modify it there, e.g. delete the part with the Approvals (I did the same here). But I bet you will figure out how it works once you have a look at the file. Best regards, Ben Christopher Short wrote: > > Hi there, > > I'm currently setting up rights for the main users of of our RT > installation. > > On a run-through with one of them, they were confused and distracted > by several sections which we won't be using but are featured rather > prominently on the site. > > These were: > > * the "Reminder" section on Tickets > > * the "New Watchers" section on the "People" tab of a > Ticket > > * The "Approval" link on the menu bar. > > > > I'm hoping hiding these sections are as easy as removing certain > rights for those user groups, especially as we'd probably still like > the sysadmin to have the ability to add Watchers. Note that these > ordinary users don't have the Watch or WatchAsAdminCC rights, so it > seems strange that they can add Watchers (even themselves). > > > > I dread hearing that the only answer is hiding those sections with CSS. > > > > Christopher > > > > ___ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: > > If you sign up for a new RT support contract before December 31, we'll take > up to 20 percent off the price. This sale won't last long, so get in touch > today. > Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. > > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
