date:20071217

[rt-users] wiki error? SetCorresponderAsCC

2007-12-17 Thread Christopher Short

I've just started using the SetCorresponderAsCC scrip contribution which can be 
found at
http://wiki.bestpractical.com/view/SetCorresponderAsCC

I thought it was a bit strange that it didn't check to see whether 
Corresponders were Owners, but in a post to this list in October, I see that 
this script did have that check previously.
http://www.gossamer-threads.com/lists/rt/users/69130

Is there some reason why this check was inappropriate enough to be removed from 
the wiki?

Christopher Short
Nexus6 Software P/L
Suite 1/3 St David St Fitzroy  Vic  3065
Email: [EMAIL PROTECTED]
Ph: +61 3 9419 1922
Fax: +61 3 9486 9712

___
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] How to implement "customer groups" or "request groups"?

2007-12-17 Thread Kenneth Crocker


Stephan, Christopher,


	We had a similar situation; we wanted requestors to see their tickets 
and any others from users in their group, but not the tickets from other 
users/requestors NOT in their group. We handled it by creating a 
front-end queue. Then we created a different queue for all the requests 
that came from the same group or type of requestors. When a request is 
sent to the front-end queue, it serves as a waiting place. In that 
queue, Requestors can see their OWN tickets, but that is all. Once that 
ticket (and any others from the same requestor-type group) has been 
reviewed and approved for work, it is moved to a queue that represents 
those common requests, basically from those requestors from the same 
group. Then we can grant group rights to that "specific" queue for the 
common group of users so everyone can see what else is in that queue, 
but not in the other queues for the other user groups. It's a little 
more work, but essentially it serves to seperate requestors into common 
groups and requires the tickets to be looked at and reviewed before 
being worked on anyway. Hope this helps.


Kenn
LBNL

On 12/17/2007 3:08 PM, Christopher Short wrote:

I was looking for something like this a little while back and didn't find an 
easy way.
The best I could find was along the lines of adding everyone relevant as 
watchers to each ticket created by someone in their group. I don't like that 
idea as I'm sure they would only occasionally need to see all tickets of their 
team-mates, not receive every update.

I'm pretty sure there isn't a right for letting you see/edit tickets created by 
your group colleagues.

Christopher

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steffen Poulsen
Sent: Tuesday, 18 December 2007 12:49 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] How to implement "customer groups" or "request groups"?

Hi,

We handle tickets from various companies in our request tracker, and
sometimes these companies ask for permission to share all tickets from
their company between themselves. A fair request I think :-)

I have put all users in a "CompanyGroup", but what rights should they be
given to be allowed to see each others tickets?

The tickets are distributed between multiple queues related to the
internal functions at our site, and they should _not_ be able to see all
the content of the queues - only the tickets created by staff in their
company.

I have searched the wiki and the mailing list, but have found nothing -
probably I am using the wrong search phrases. Any ideas or best
practices?

Best regards,

Steffen
___
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



___
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] How to implement "customer groups" or "request groups"?

2007-12-17 Thread Christopher Short

I was looking for something like this a little while back and didn't find an 
easy way.
The best I could find was along the lines of adding everyone relevant as 
watchers to each ticket created by someone in their group. I don't like that 
idea as I'm sure they would only occasionally need to see all tickets of their 
team-mates, not receive every update.

I'm pretty sure there isn't a right for letting you see/edit tickets created by 
your group colleagues.

Christopher

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steffen Poulsen
Sent: Tuesday, 18 December 2007 12:49 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] How to implement "customer groups" or "request groups"?

Hi,

We handle tickets from various companies in our request tracker, and
sometimes these companies ask for permission to share all tickets from
their company between themselves. A fair request I think :-)

I have put all users in a "CompanyGroup", but what rights should they be
given to be allowed to see each others tickets?

The tickets are distributed between multiple queues related to the
internal functions at our site, and they should _not_ be able to see all
the content of the queues - only the tickets created by staff in their
company.

I have searched the wiki and the mailing list, but have found nothing -
probably I am using the wrong search phrases. Any ideas or best
practices?

Best regards,

Steffen
___
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] Not sure what is wrong with rt-mailgate

2007-12-17 Thread Mike Gracy


I get the same output in /var/log/maillog if I email the queue.
I'm thinking this might be a misconfiguration with the web server.  Is 
rt-mailgate calling something via the httpd service to input the ticket?


[EMAIL PROTECTED] bin]# ./rt-mailgate --action correspond --queue General --url 
http://rt.mypointscorp.com

From:[EMAIL PROTECTED]
Subject:This is a test
This is a test
.
RT server error.

The RT server which handled your email did not behave as expected. It
said:

%# BEGIN BPS TAGGED BLOCK {{{
%#
%# COPYRIGHT:
%#
%# This software is Copyright (c) 1996-2007 Best Practical Solutions, LLC
%#  <[EMAIL PROTECTED]>
%#
%# (Except where explicitly superseded by other copyright notices)
%#
%#
%# LICENSE:
%#
%# This work is made available to you under the terms of Version 2 of
%# the GNU General Public License. A copy of that license should have
%# been provided with this software, but in any event can be snarfed
%# from www.gnu.org.
%#
%# This work is distributed in the hope that it will be useful, but
%# WITHOUT ANY WARRANTY; without even the implied warranty of
%# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
%# General Public License for more details.
%#
%# You should have received a copy of the GNU General Public License
%# along with this program; if not, write to the Free Software
%# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
%# 02110-1301 or visit their web page on the internet at
%# http://www.gnu.org/copyleft/gpl.html.
%#
%#
%# CONTRIBUTION SUBMISSION POLICY:
%#
%# (The following paragraph is not intended to limit the rights granted
%# to you to modify and distribute this software under the terms of
%# the GNU General Public License and is only of importance to you if
%# you choose to contribute your changes and enhancements to the
%# community by submitting them to Best Practical Solutions, LLC.)
%#
%# By intentionally submitting any modifications, corrections or
%# derivatives to this work, or any other work intended for use with
%# Request Tracker, to Best Practical Solutions, LLC, you confirm that
%# you are the copyright holder for those contributions and you grant
%# Best Practical Solutions,  LLC a nonexclusive, worldwide, irrevocable,
%# royalty-free, perpetual, license to use, copy, create derivative
%# works based on those contributions, and sublicense and distribute
%# those contributions and any derivatives thereof.
%#
%# END BPS TAGGED BLOCK }}}
<%flags>
inherit => undef # inhibit UTF8 conversion done in /autohandler

<%ARGS>
$queue => 1
$action => "correspond"
$ticket => undef

<%init>
$m->comp('/Elements/Callback', _CallbackName => 'Pre', %ARGS);
use RT::Interface::Email ();# It's an exporter, but we don't care
$r->content_type('text/plain; charset=utf-8');
$m->error_format('text');
my ( $status, $error, $Ticket ) = RT::Interface::Email::Gateway( \%ARGS );
if ( $status == 1 ) {
 $m->out('ok');
 if ( $Ticket->Id ) {
   $m->out( 'Ticket: '  . ($Ticket->Id || '') );
   $m->out( 'Queue: '   . ($Ticket->QueueObj->Name || '') );
   $m->out( 'Owner: '   . ($Ticket->OwnerObj->Name || '') );
   $m->out( 'Status: '  . ($Ticket->Status || '') );
   $m->out( 'Subject: ' . ($Ticket->Subject|| '') );
   $m->out(
 'Requestor: ' . ($Ticket->Requestors->MemberEmailAddressesAsString 
|| '') );

 }
}
else {
 $RT::Logger->error( "Could not record email: " . $error );
 if ( $status == -75 ) {
   $m->out( "temporary failure - " . $error );
 }
 else {
   $m->out( 'not ok - ' . $error );
 }
}
$m->abort();


--
Mike Gracy
www.MyPoints.com
Unix/Network Sysadmin

525 Market St.
34th Floor
San Francisco, Ca 94105

Desk-415.829.6174
Fax-415-829-6174

___
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] Trouble after upgrade

2007-12-17 Thread Joshua Speer

I upgraded to 1.50 using CPAN:

  
our $VERSION = "1.50";


--- Drew Barnes <[EMAIL PROTECTED]> wrote:

> What version of SearchBuilder are you using?  I
> notice that initially
> you list it as 1.45 whereas 1.49 (at least) is out.
> 
> Joshua Speer wrote:
> > Drew, 
> >
> > Thanks again for your replies. I had found that
> thread
> > last week when you first started helping me.
> > Unfortunately this wasn't the fix for me. I have
> been
> > searching the gossamer threads looking for
> anything
> > that might be a possibility, but haven't found the
> fix
> > yet.
> >
> > --- Drew Barnes <[EMAIL PROTECTED]>
> wrote:
> >
> >   
> >> This post from April regarded Reminders, but it
> >> seems very much like the
> >> problem you are describing.
> >> Found my problem. Turns out I had an old
> >> DBIx::SearchBuilder installed
> >> *in* a
> >> different dir (from an old Perl install), and
> >> somehow it was being used
> >> instead of the new one. I deleted the old DBIx,
> >> cleaned the Mason cache,
> >> restarted httpd, and all's well now with
> Reminders.
> >>
> >> hope that helps someone;
> >>
> >> -- Gary Oberbrunner
> >>
> >> I would start a CPAN shell and install
> >> DBIx::SearchBuilder to make sure
> >> you have the latest.
> >>
> >>
> >> Joshua Speer wrote:
> >> 
> >>> OK so here is the latest, I have put the source
> on
> >>>   
> >> the
> >> 
> >>> server, and ran make depends, and all
> dependancies
> >>> have been satisfied. Also, I have removed and
> >>> conflicting older packages. This appears to be
> >>> something with the new implementation of
> >>>   
> >> reminders,
> >> 
> >>> and mason not being configured for it properly?
> Is
> >>> their any location that needs to have reminders
> >>> specified for mason?
> >>>
> >>> Thanks,
> >>>
> >>> Josh
> >>>
> >>> --- Drew Barnes <[EMAIL PROTECTED]>
> >>>   
> >> wrote:
> >> 
> >>>   
> >>>   
>  Not exactly the same error but similar. 
> Perhaps
>  this can either help or
>  get you started poking through things.
> 
>  
>  
> >
>
http://www.gossamer-threads.com/lists/rt/users/64920#64920
> >   
> >>>   
> >>>   
>  Joshua Speer wrote:
>  
>  
> > Here is the raw error when I try to create a
> new
> > ticket:
> >
> > RT::CustomField::MatchPattern Unimplemented in
> > HTML::Mason::Commands.
> >
> >   
> >   
> >
>
(/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> >   
> >>>   
> >>>   
> > line 65) 
> >
> >
> > Trace begun at
> > /usr/share/perl5/HTML/Mason/Exceptions.pm line
> >   
> >> 129
> >> 
> >   
> >   
> >
>
HTML::Mason::Exceptions::rethrow_exception('RT::CustomField::MatchPattern
> >   
> >>>   
> >>>   
> > Unimplemented in HTML::Mason::Commands.
> >
> >   
> >   
> >
>
(/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> >   
> >>>   
> >>>   
> > line 65) ^J') called at
> > /usr/share/perl5/DBIx/SearchBuilder/Record.pm
> >   
> >> line
> >> 
> >   
> >   
>  495
>  
>  
> >
>
DBIx::SearchBuilder::Record::AUTOLOAD('RT::CustomField=HASH(0x8324654)',
> >   
> >>>   
> >>>   
> > undef) called at
> >
> >   
> >   
> >
>
/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> >   
> >>>   
> >>>   
> > line 65
> >
> HTML::Mason::Commands::__ANON__('CustomFields',
> > 'RT::CustomFields=HASH(0x9af2760)', 'ARGSRef',
> > 'HASH(0x960f230)') called at
> > /usr/share/perl5/HTML/Mason/Component.pm line
> >   
> >> 135
> >> 
> >   
> >   
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x83240c0)',
> >   
> >>>   
> >>>   
> > 'CustomFields',
> >   
> >   
>  'RT::CustomFields=HASH(0x9af2760)',
>  
>  
> > 'ARGSRef', 'HASH(0x960f230)') called at
> > /usr/share/perl5/HTML/Mason/Request.pm line
> 1251
> > eval {...} at
> >   
> >   
>  /usr/share/perl5/HTML/Mason/Request.pm
>  
>  
> > line 1246
> > HTML::Mason::Request::comp(undef, undef,
> > 'CustomFields',
> >   
> >   
>  'RT::CustomFields=HASH(0x9af2760)',
>  
>  
> > 'ARGSRef', 'HASH(0x960f230)') called at
> >
> >   
> >   
> >
>
/usr/share/request-tracker3.6/html/Ticket/Create.html
> >   
> >>>   
> >>>   
> > line 247
> > HTML::Mason::Commands::__ANON__('Queue', 4,
> 
=== message truncated ===



  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
__

Re: [rt-users] Trouble after upgrade

2007-12-17 Thread Drew Barnes

What version of SearchBuilder are you using?  I notice that initially
you list it as 1.45 whereas 1.49 (at least) is out.

Joshua Speer wrote:
> Drew, 
>
> Thanks again for your replies. I had found that thread
> last week when you first started helping me.
> Unfortunately this wasn't the fix for me. I have been
> searching the gossamer threads looking for anything
> that might be a possibility, but haven't found the fix
> yet.
>
> --- Drew Barnes <[EMAIL PROTECTED]> wrote:
>
>   
>> This post from April regarded Reminders, but it
>> seems very much like the
>> problem you are describing.
>> Found my problem. Turns out I had an old
>> DBIx::SearchBuilder installed
>> *in* a
>> different dir (from an old Perl install), and
>> somehow it was being used
>> instead of the new one. I deleted the old DBIx,
>> cleaned the Mason cache,
>> restarted httpd, and all's well now with Reminders.
>>
>> hope that helps someone;
>>
>> -- Gary Oberbrunner
>>
>> I would start a CPAN shell and install
>> DBIx::SearchBuilder to make sure
>> you have the latest.
>>
>>
>> Joshua Speer wrote:
>> 
>>> OK so here is the latest, I have put the source on
>>>   
>> the
>> 
>>> server, and ran make depends, and all dependancies
>>> have been satisfied. Also, I have removed and
>>> conflicting older packages. This appears to be
>>> something with the new implementation of
>>>   
>> reminders,
>> 
>>> and mason not being configured for it properly? Is
>>> their any location that needs to have reminders
>>> specified for mason?
>>>
>>> Thanks,
>>>
>>> Josh
>>>
>>> --- Drew Barnes <[EMAIL PROTECTED]>
>>>   
>> wrote:
>> 
>>>   
>>>   
 Not exactly the same error but similar.  Perhaps
 this can either help or
 get you started poking through things.

 
 
> http://www.gossamer-threads.com/lists/rt/users/64920#64920
>   
>>>   
>>>   
 Joshua Speer wrote:
 
 
> Here is the raw error when I try to create a new
> ticket:
>
> RT::CustomField::MatchPattern Unimplemented in
> HTML::Mason::Commands.
>
>   
>   
> (/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
>   
>>>   
>>>   
> line 65) 
>
>
> Trace begun at
> /usr/share/perl5/HTML/Mason/Exceptions.pm line
>   
>> 129
>> 
>   
>   
> HTML::Mason::Exceptions::rethrow_exception('RT::CustomField::MatchPattern
>   
>>>   
>>>   
> Unimplemented in HTML::Mason::Commands.
>
>   
>   
> (/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
>   
>>>   
>>>   
> line 65) ^J') called at
> /usr/share/perl5/DBIx/SearchBuilder/Record.pm
>   
>> line
>> 
>   
>   
 495
 
 
> DBIx::SearchBuilder::Record::AUTOLOAD('RT::CustomField=HASH(0x8324654)',
>   
>>>   
>>>   
> undef) called at
>
>   
>   
> /usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
>   
>>>   
>>>   
> line 65
> HTML::Mason::Commands::__ANON__('CustomFields',
> 'RT::CustomFields=HASH(0x9af2760)', 'ARGSRef',
> 'HASH(0x960f230)') called at
> /usr/share/perl5/HTML/Mason/Component.pm line
>   
>> 135
>> 
>   
>   
> HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x83240c0)',
>   
>>>   
>>>   
> 'CustomFields',
>   
>   
 'RT::CustomFields=HASH(0x9af2760)',
 
 
> 'ARGSRef', 'HASH(0x960f230)') called at
> /usr/share/perl5/HTML/Mason/Request.pm line 1251
> eval {...} at
>   
>   
 /usr/share/perl5/HTML/Mason/Request.pm
 
 
> line 1246
> HTML::Mason::Request::comp(undef, undef,
> 'CustomFields',
>   
>   
 'RT::CustomFields=HASH(0x9af2760)',
 
 
> 'ARGSRef', 'HASH(0x960f230)') called at
>
>   
>   
> /usr/share/request-tracker3.6/html/Ticket/Create.html
>   
>>>   
>>>   
> line 247
> HTML::Mason::Commands::__ANON__('Queue', 4,
>   
>   
 'Queue',
 
 
> 4) called at
>   
>   
 /usr/share/perl5/HTML/Mason/Component.pm
 
 
> line 135
>
>   
>   
> HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x97fa2f0)',
>   
>>>   
>>>   
> 'Queue', 4, 'Queue', 4) called at
> /usr/share/perl5/HTML/Mason/Request.pm line 1256
> eval {...} at
>   
>   
 /usr/share/perl5/HTML/Mason/Request.pm
 
 
> line 1246
> HTML::Mason::Request::comp(undef, undef, undef,
> 'Queue', 4, 'Queue', 4) called at
> /usr/share/perl5/HTML/Mason/Request.pm line 915
>
>   
>   
> HTML::Mason::Request::call_

Re: [rt-users] Trouble after upgrade

2007-12-17 Thread Joshua Speer

Drew, 

Thanks again for your replies. I had found that thread
last week when you first started helping me.
Unfortunately this wasn't the fix for me. I have been
searching the gossamer threads looking for anything
that might be a possibility, but haven't found the fix
yet.

--- Drew Barnes <[EMAIL PROTECTED]> wrote:

> This post from April regarded Reminders, but it
> seems very much like the
> problem you are describing.
> Found my problem. Turns out I had an old
> DBIx::SearchBuilder installed
> *in* a
> different dir (from an old Perl install), and
> somehow it was being used
> instead of the new one. I deleted the old DBIx,
> cleaned the Mason cache,
> restarted httpd, and all's well now with Reminders.
> 
> hope that helps someone;
> 
> -- Gary Oberbrunner
> 
> I would start a CPAN shell and install
> DBIx::SearchBuilder to make sure
> you have the latest.
> 
> 
> Joshua Speer wrote:
> > OK so here is the latest, I have put the source on
> the
> > server, and ran make depends, and all dependancies
> > have been satisfied. Also, I have removed and
> > conflicting older packages. This appears to be
> > something with the new implementation of
> reminders,
> > and mason not being configured for it properly? Is
> > their any location that needs to have reminders
> > specified for mason?
> >
> > Thanks,
> >
> > Josh
> >
> > --- Drew Barnes <[EMAIL PROTECTED]>
> wrote:
> >
> >   
> >> Not exactly the same error but similar.  Perhaps
> >> this can either help or
> >> get you started poking through things.
> >>
> >> 
> >
>
http://www.gossamer-threads.com/lists/rt/users/64920#64920
> >   
> >> Joshua Speer wrote:
> >> 
> >>> Here is the raw error when I try to create a new
> >>> ticket:
> >>>
> >>> RT::CustomField::MatchPattern Unimplemented in
> >>> HTML::Mason::Commands.
> >>>
> >>>   
> >
>
(/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> >   
> >>> line 65) 
> >>>
> >>>
> >>> Trace begun at
> >>> /usr/share/perl5/HTML/Mason/Exceptions.pm line
> 129
> >>>
> >>>   
> >
>
HTML::Mason::Exceptions::rethrow_exception('RT::CustomField::MatchPattern
> >   
> >>> Unimplemented in HTML::Mason::Commands.
> >>>
> >>>   
> >
>
(/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> >   
> >>> line 65) ^J') called at
> >>> /usr/share/perl5/DBIx/SearchBuilder/Record.pm
> line
> >>>   
> >> 495
> >> 
> >
>
DBIx::SearchBuilder::Record::AUTOLOAD('RT::CustomField=HASH(0x8324654)',
> >   
> >>> undef) called at
> >>>
> >>>   
> >
>
/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> >   
> >>> line 65
> >>> HTML::Mason::Commands::__ANON__('CustomFields',
> >>> 'RT::CustomFields=HASH(0x9af2760)', 'ARGSRef',
> >>> 'HASH(0x960f230)') called at
> >>> /usr/share/perl5/HTML/Mason/Component.pm line
> 135
> >>>
> >>>   
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x83240c0)',
> >   
> >>> 'CustomFields',
> >>>   
> >> 'RT::CustomFields=HASH(0x9af2760)',
> >> 
> >>> 'ARGSRef', 'HASH(0x960f230)') called at
> >>> /usr/share/perl5/HTML/Mason/Request.pm line 1251
> >>> eval {...} at
> >>>   
> >> /usr/share/perl5/HTML/Mason/Request.pm
> >> 
> >>> line 1246
> >>> HTML::Mason::Request::comp(undef, undef,
> >>> 'CustomFields',
> >>>   
> >> 'RT::CustomFields=HASH(0x9af2760)',
> >> 
> >>> 'ARGSRef', 'HASH(0x960f230)') called at
> >>>
> >>>   
> >
>
/usr/share/request-tracker3.6/html/Ticket/Create.html
> >   
> >>> line 247
> >>> HTML::Mason::Commands::__ANON__('Queue', 4,
> >>>   
> >> 'Queue',
> >> 
> >>> 4) called at
> >>>   
> >> /usr/share/perl5/HTML/Mason/Component.pm
> >> 
> >>> line 135
> >>>
> >>>   
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x97fa2f0)',
> >   
> >>> 'Queue', 4, 'Queue', 4) called at
> >>> /usr/share/perl5/HTML/Mason/Request.pm line 1256
> >>> eval {...} at
> >>>   
> >> /usr/share/perl5/HTML/Mason/Request.pm
> >> 
> >>> line 1246
> >>> HTML::Mason::Request::comp(undef, undef, undef,
> >>> 'Queue', 4, 'Queue', 4) called at
> >>> /usr/share/perl5/HTML/Mason/Request.pm line 915
> >>>
> >>>   
> >
>
HTML::Mason::Request::call_next('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)',
> >   
> >>> 'Queue', 4) called at
> >>> /usr/share/request-tracker3.6/html/autohandler
> >>>   
> >> line
> >> 
> >>> 279
> >>> HTML::Mason::Commands::__ANON__('Queue', 4)
> called
> >>>   
> >> at
> >> 
> >>> /usr/share/perl5/HTML/Mason/Component.pm line
> 135
> >>>
> >>>   
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x87f0858)',
> >   
> >>> 'Queue', 4) called at
> >>> /usr/share/perl5/HTML/Mason/Request.pm line 1251
> >>> eval {...} at
> >>>   
> >> /usr/share/perl5/HTML/Mason/Request.pm
> >> 
> >>> line 1246
> >>> HTML::Mason::Request::comp(undef, undef, undef,
> >>> 'Queue', 4) called at
> >>> /usr/share/perl5/HTML/Mason/Request.pm line 460
> >>> eval {...} at
> >>>   
> >

Re: [rt-users] Having problems with a default install of 3.6.5

2007-12-17 Thread Mike Gracy

Ok, I'll think about it.  It's just that in the menubar I found 
inconsistencies.  Some links had the /index.html, others didn't.  That's 
what led me to believe it was a minor typo.


Drew Barnes wrote:

I'm not sure that's a bug, per se.  I know some people use some rewrite
rules to add index.html to any path with no file (whether for security
reasons or for ease of use on a per-site basis), although you should be
able to set an option in httpd.conf to use that by default also (I think).

Jesse is very active on the list here, so you could always send a diff
-u to rt-devel if you feel it absolutely should be fixed for future
releases.  I don't have any problems on my site with that particular
file as it is, though.


Mike Gracy wrote:
  

Well I did finally get logging working to /var/log/rt3.
I also finally found and fixed the defective href link to the Admin
interface.

My diff for rt3/share/html/Elements/Tabs :
87c87
 'Admin/',
---


   path => 'Admin/index.html',
  

I've even downloaded the source again to make sure.  3.6.5 still has
this error in the tar.gz file.

I find it hard to believe that this simple error hasn't been patched
yet.  Do the developers monitor this list for these types of things?


Drew Barnes wrote:


Not sure about your other issues, but if you touch rt.log in
/opt/rt3/var/log, the error with logging will go away.

Mike Gracy wrote:
  

I configured and installed it, I can login with the default root
account.
I click on Configuration and get sent back to the Home - RT at a
glance page.
I'm unable to get to the config page.  I've been scouring the httpd
error and system messages log and not finding anything that helps.
I tried turning on the log file in SiteConfig, but that errored out,
stating that it couldn't open/create rt.log.  I should think the
default permissions to /opt/rt3/var/log would have allowed for this
automatically.   I'm at a bit of a loss here.
I'm needing to solve this because I need to migrate a 3.0.12 database
from another machine to this one.  I've already done the db import and
upgrades without error, but it does me no good if I can't get in the
Configuration page.
Help?





--
Mike Gracy
www.MyPoints.com
Unix/Network Sysadmin

525 Market St.
34th Floor
San Francisco, Ca 94105

Desk-415.829.6174
Fax-415-829-6174

___
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] Trouble after upgrade

2007-12-17 Thread Drew Barnes

This post from April regarded Reminders, but it seems very much like the
problem you are describing.
Found my problem. Turns out I had an old DBIx::SearchBuilder installed
*in* a
different dir (from an old Perl install), and somehow it was being used
instead of the new one. I deleted the old DBIx, cleaned the Mason cache,
restarted httpd, and all's well now with Reminders.

hope that helps someone;

-- Gary Oberbrunner

I would start a CPAN shell and install DBIx::SearchBuilder to make sure
you have the latest.


Joshua Speer wrote:
> OK so here is the latest, I have put the source on the
> server, and ran make depends, and all dependancies
> have been satisfied. Also, I have removed and
> conflicting older packages. This appears to be
> something with the new implementation of reminders,
> and mason not being configured for it properly? Is
> their any location that needs to have reminders
> specified for mason?
>
> Thanks,
>
> Josh
>
> --- Drew Barnes <[EMAIL PROTECTED]> wrote:
>
>   
>> Not exactly the same error but similar.  Perhaps
>> this can either help or
>> get you started poking through things.
>>
>> 
> http://www.gossamer-threads.com/lists/rt/users/64920#64920
>   
>> Joshua Speer wrote:
>> 
>>> Here is the raw error when I try to create a new
>>> ticket:
>>>
>>> RT::CustomField::MatchPattern Unimplemented in
>>> HTML::Mason::Commands.
>>>
>>>   
> (/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
>   
>>> line 65) 
>>>
>>>
>>> Trace begun at
>>> /usr/share/perl5/HTML/Mason/Exceptions.pm line 129
>>>
>>>   
> HTML::Mason::Exceptions::rethrow_exception('RT::CustomField::MatchPattern
>   
>>> Unimplemented in HTML::Mason::Commands.
>>>
>>>   
> (/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
>   
>>> line 65) ^J') called at
>>> /usr/share/perl5/DBIx/SearchBuilder/Record.pm line
>>>   
>> 495
>> 
> DBIx::SearchBuilder::Record::AUTOLOAD('RT::CustomField=HASH(0x8324654)',
>   
>>> undef) called at
>>>
>>>   
> /usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
>   
>>> line 65
>>> HTML::Mason::Commands::__ANON__('CustomFields',
>>> 'RT::CustomFields=HASH(0x9af2760)', 'ARGSRef',
>>> 'HASH(0x960f230)') called at
>>> /usr/share/perl5/HTML/Mason/Component.pm line 135
>>>
>>>   
> HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x83240c0)',
>   
>>> 'CustomFields',
>>>   
>> 'RT::CustomFields=HASH(0x9af2760)',
>> 
>>> 'ARGSRef', 'HASH(0x960f230)') called at
>>> /usr/share/perl5/HTML/Mason/Request.pm line 1251
>>> eval {...} at
>>>   
>> /usr/share/perl5/HTML/Mason/Request.pm
>> 
>>> line 1246
>>> HTML::Mason::Request::comp(undef, undef,
>>> 'CustomFields',
>>>   
>> 'RT::CustomFields=HASH(0x9af2760)',
>> 
>>> 'ARGSRef', 'HASH(0x960f230)') called at
>>>
>>>   
> /usr/share/request-tracker3.6/html/Ticket/Create.html
>   
>>> line 247
>>> HTML::Mason::Commands::__ANON__('Queue', 4,
>>>   
>> 'Queue',
>> 
>>> 4) called at
>>>   
>> /usr/share/perl5/HTML/Mason/Component.pm
>> 
>>> line 135
>>>
>>>   
> HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x97fa2f0)',
>   
>>> 'Queue', 4, 'Queue', 4) called at
>>> /usr/share/perl5/HTML/Mason/Request.pm line 1256
>>> eval {...} at
>>>   
>> /usr/share/perl5/HTML/Mason/Request.pm
>> 
>>> line 1246
>>> HTML::Mason::Request::comp(undef, undef, undef,
>>> 'Queue', 4, 'Queue', 4) called at
>>> /usr/share/perl5/HTML/Mason/Request.pm line 915
>>>
>>>   
> HTML::Mason::Request::call_next('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)',
>   
>>> 'Queue', 4) called at
>>> /usr/share/request-tracker3.6/html/autohandler
>>>   
>> line
>> 
>>> 279
>>> HTML::Mason::Commands::__ANON__('Queue', 4) called
>>>   
>> at
>> 
>>> /usr/share/perl5/HTML/Mason/Component.pm line 135
>>>
>>>   
> HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x87f0858)',
>   
>>> 'Queue', 4) called at
>>> /usr/share/perl5/HTML/Mason/Request.pm line 1251
>>> eval {...} at
>>>   
>> /usr/share/perl5/HTML/Mason/Request.pm
>> 
>>> line 1246
>>> HTML::Mason::Request::comp(undef, undef, undef,
>>> 'Queue', 4) called at
>>> /usr/share/perl5/HTML/Mason/Request.pm line 460
>>> eval {...} at
>>>   
>> /usr/share/perl5/HTML/Mason/Request.pm
>> 
>>> line 460
>>> eval {...} at
>>>   
>> /usr/share/perl5/HTML/Mason/Request.pm
>> 
>>> line 412
>>>
>>>   
> HTML::Mason::Request::exec('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)')
>   
>>> called at
>>>   
>> /usr/share/perl5/HTML/Mason/ApacheHandler.pm
>> 
>>> line 165
>>>
>>>   
> HTML::Mason::Request::ApacheHandler::exec('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)')
>   
>>> called at
>>>   
>> /usr/share/perl5/HTML/Mason/ApacheHandler.pm
>> 
>>> line 832
>>>
>>>   
> HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x924cc4c)',
>   
>>> 'Apache=SCALA

Re: R: R: [rt-users] Having problems with a default install of 3.6.5

2007-12-17 Thread Mike Gracy


Thanks for the feedback.  I'll remember to hit reply to all next time.
I'll look at the apache config.
Gianluca Cecchi wrote:

I was only able to read your answer some minutes ago.. Next time please send 
messages to all the list, so that eventually other guys could give quicker 
replies...

The 'Configuration' link resolves to the same page as yours for me, so it 
doesn't seem a problem about rt itself.
When you have a link pointing to a directory, it defaults to some kind of page 
into that directory, tipically index.hmtl.
You define it inside apache configuration file (/etc/httpd/conf/httpd.conf on 
my fc6).

Pehaps your apache config is different form the default one...
The directive inside httpd.conf is DirectoryIndex and it is this one below for 
me:

# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents.  The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var

I have also this in my rt3.conf file (see in particular the "RedirectMatch" entry) under /etc/httpd/conf.d/. 
Don't know if could be another source of problems if misconfigured:


Alias /rt3 "/usr/share/rt3/html"

PerlModule Apache::DBI
PerlRequire /usr/sbin/webmux.pl


  AllowOverride All
  Options ExecCGI FollowSymLinks



  RewriteEngine On
  RedirectMatch permanent (.*)/$ $1/index.html
  AddDefaultCharset UTF-8
  SetHandler perl-script
  PerlHandler RT::Mason



  

-Messaggio originale-
Da: Mike Gracy [mailto:[EMAIL PROTECTED] 
Inviato: venerdì 14 dicembre 2007 21.54

A: Gianluca Cecchi
Oggetto: Re: R: [rt-users] Having problems with a default 
install of 3.6.5


Ok, I updated the logging path in RT_SiteConfig.pm and set up 
the same dir below.  Logging works now.  Thanks.


I just discovered what is happening with the 'Configuration' link.
It is resolving as 'rt./Admin/'.  It should 
have 'index.html' on the end of it.  When I put the 
'index.html' on the end, it works perfectly.  Which file can 
I edit to fix this?




--
Mike Gracy
www.MyPoints.com
Unix/Network Sysadmin

525 Market St.
34th Floor
San Francisco, Ca 94105

Desk-415.829.6174
Fax-415-829-6174

___
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] bounce handling -- rtbouncehandler download link or alternatives

2007-12-17 Thread Roedel, Mark

Is anyone aware of a download link for rtbouncehandler documented at
http://rt.bestpractical.com/view/RtBounceHandler?  (That page in the
wiki -- presumably copied and pasted from elsewhere -- simply says that
the Perl source "is an attachment to this ticket."  Googling brought up
a few posts from the mailing list archives and links to the wiki page,
but nothing that indicated where it could be downloaded from.  I also
tried searching the RT issue tracker, but didn't come up with any
matches there either.)

Alternately, what other mechanisms exist for alerting the owner of a
ticket when a requestor's or watcher's address associated with the
ticket is generating bounce messages?

Thanks!


--
Mark Roedel
Senior Programmer / Analyst
LeTourneau University
Longview, Texas  USA
___
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] Trouble after upgrade

2007-12-17 Thread Joshua Speer

OK so here is the latest, I have put the source on the
server, and ran make depends, and all dependancies
have been satisfied. Also, I have removed and
conflicting older packages. This appears to be
something with the new implementation of reminders,
and mason not being configured for it properly? Is
their any location that needs to have reminders
specified for mason?

Thanks,

Josh

--- Drew Barnes <[EMAIL PROTECTED]> wrote:

> Not exactly the same error but similar.  Perhaps
> this can either help or
> get you started poking through things.
>
http://www.gossamer-threads.com/lists/rt/users/64920#64920
> 
> 
> Joshua Speer wrote:
> > Here is the raw error when I try to create a new
> > ticket:
> >
> > RT::CustomField::MatchPattern Unimplemented in
> > HTML::Mason::Commands.
> >
>
(/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> > line 65) 
> >
> >
> > Trace begun at
> > /usr/share/perl5/HTML/Mason/Exceptions.pm line 129
> >
>
HTML::Mason::Exceptions::rethrow_exception('RT::CustomField::MatchPattern
> > Unimplemented in HTML::Mason::Commands.
> >
>
(/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> > line 65) ^J') called at
> > /usr/share/perl5/DBIx/SearchBuilder/Record.pm line
> 495
> >
>
DBIx::SearchBuilder::Record::AUTOLOAD('RT::CustomField=HASH(0x8324654)',
> > undef) called at
> >
>
/usr/share/request-tracker3.6/html/Elements/ValidateCustomFields
> > line 65
> > HTML::Mason::Commands::__ANON__('CustomFields',
> > 'RT::CustomFields=HASH(0x9af2760)', 'ARGSRef',
> > 'HASH(0x960f230)') called at
> > /usr/share/perl5/HTML/Mason/Component.pm line 135
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x83240c0)',
> > 'CustomFields',
> 'RT::CustomFields=HASH(0x9af2760)',
> > 'ARGSRef', 'HASH(0x960f230)') called at
> > /usr/share/perl5/HTML/Mason/Request.pm line 1251
> > eval {...} at
> /usr/share/perl5/HTML/Mason/Request.pm
> > line 1246
> > HTML::Mason::Request::comp(undef, undef,
> > 'CustomFields',
> 'RT::CustomFields=HASH(0x9af2760)',
> > 'ARGSRef', 'HASH(0x960f230)') called at
> >
>
/usr/share/request-tracker3.6/html/Ticket/Create.html
> > line 247
> > HTML::Mason::Commands::__ANON__('Queue', 4,
> 'Queue',
> > 4) called at
> /usr/share/perl5/HTML/Mason/Component.pm
> > line 135
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x97fa2f0)',
> > 'Queue', 4, 'Queue', 4) called at
> > /usr/share/perl5/HTML/Mason/Request.pm line 1256
> > eval {...} at
> /usr/share/perl5/HTML/Mason/Request.pm
> > line 1246
> > HTML::Mason::Request::comp(undef, undef, undef,
> > 'Queue', 4, 'Queue', 4) called at
> > /usr/share/perl5/HTML/Mason/Request.pm line 915
> >
>
HTML::Mason::Request::call_next('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)',
> > 'Queue', 4) called at
> > /usr/share/request-tracker3.6/html/autohandler
> line
> > 279
> > HTML::Mason::Commands::__ANON__('Queue', 4) called
> at
> > /usr/share/perl5/HTML/Mason/Component.pm line 135
> >
>
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x87f0858)',
> > 'Queue', 4) called at
> > /usr/share/perl5/HTML/Mason/Request.pm line 1251
> > eval {...} at
> /usr/share/perl5/HTML/Mason/Request.pm
> > line 1246
> > HTML::Mason::Request::comp(undef, undef, undef,
> > 'Queue', 4) called at
> > /usr/share/perl5/HTML/Mason/Request.pm line 460
> > eval {...} at
> /usr/share/perl5/HTML/Mason/Request.pm
> > line 460
> > eval {...} at
> /usr/share/perl5/HTML/Mason/Request.pm
> > line 412
> >
>
HTML::Mason::Request::exec('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)')
> > called at
> /usr/share/perl5/HTML/Mason/ApacheHandler.pm
> > line 165
> >
>
HTML::Mason::Request::ApacheHandler::exec('HTML::Mason::Request::ApacheHandler=HASH(0x859eec8)')
> > called at
> /usr/share/perl5/HTML/Mason/ApacheHandler.pm
> > line 832
> >
>
HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x924cc4c)',
> > 'Apache=SCALAR(0x8c24b30)') called at
> > /usr/share/request-tracker3.4/libexec/webmux.pl
> line
> > 124
> > eval {...} at
> > /usr/share/request-tracker3.4/libexec/webmux.pl
> line
> > 124
> > RT::Mason::handler('Apache=SCALAR(0x8c24b30)')
> called
> > at /dev/null line 0
> > eval {...} at /dev/null line 0
> >
> >
> >
> > --- Drew Barnes <[EMAIL PROTECTED]>
> wrote:
> >
> >   
> >> Ok.  It looks like something didn't upgrade
> >> properly.  Can't help you on
> >> the Debian upgrade since I always go from source
> and
> >> haven't touched
> >> Debian in years.
> >>
> >> It may help to search the lists in a slightly
> more
> >> friendly fashion,
> >> such as http://www.gossamer-threads.com/lists/rt/
> >>
> >>
> >> Joshua Speer wrote:
> >> 
> >>> I ran the commands from the README output is
> >>>   
> >> below:
> >> 
> >>> /opt/rt3/sbin/rt-setup-database --action schema
> \
> >>>--datadir etc/upgrade/
> >>>/opt/rt3/sbin/rt-setup-database --action
> >>>   
> >> acl \
> >> 
> >>>--datadir etc/upgrade/
> >>>

[rt-users] Create Ticket on Resolve, but only if Custom Field is....

2007-12-17 Thread Matt Westfall

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

OK, I am getting ever so closer to getting this to work.

I have two Custom Fields:  Billable and Followup.

I want to create a followup ticket if Followup is Yes.
I want to create an invoice ticket if Billable is Yes/Covered/or/Gratis

Here is my Billable scrip code:

Condition User Defined
Action Create Tickets
Template Global Template Create-Invoice

return 0 unless $self->TransactionObj->Type eq "Resolved";
return 0 unless $self->TicketObj->FirstCustomFieldValue('Billable') =~
/Yes/i;
return 0 unless $self->TicketObj->FirstCustomFieldValue('Billable') =~
/Covered/i;
return 0 unless $self->TicketObj->FirstCustomFieldValue('Billable') =~
/Gratis/i;
$RT::Logger->debug("Scrip running");
1;

and the Billable Template:

===Create-Ticket: generate-invoice
Queue:  Accounting
Subject: Invoice: { $Tickets{'TOP'} -> Subject() }
Requestor: {$Tickets{'TOP'}->OwnerObj->EmailAddress() }
RefersTo:  {$Tickets{'TOP'}->Id() }
Content: Please generate an invoice for this customer.
Billable was set to:
{$Tickets}{'TOP'}->TicketObj->FirstCustomFieldValue('Billable')}

Billable hours was set to:
{$Tickets}{'TOP'}->TicketObj->FirstCustomFieldValue('Billable Hours')}
Please refer to previous ticket for more information.
ENDOFCONTENT

For Followup:

Condition User Defined
Action Create Ticket
Template Global Template Generate-Followup

===Create-Ticket: generate-followup
Queue:  Customer Service
Subject: Invoice: { $Tickets{'TOP'} -> Subject() }
Requestor: {$Tickets{'TOP'}->OwnerObj->EmailAddress() }
RefersTo:  {$Tickets{'TOP'}->Id() }
Content: A follow up was requested on this ticket.  Please refer to
previous ticket for more information.
ENDOFCONTENT


When I resolve a ticket which has Yes in both fields, there are various
entries in the /var/log/messages, but none of them refer to scrip 22 or 23.

- From the RT_Config.pm debug messages should go to syslog or
/var/log/messages, but nothing is mentioned there.

I would greatly appreciate any help in finally nailing this down.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHZoh3b/8X6V5MpAURAr8QAKDhk+ILJ2t9mjt68sKdXBmw8MljQACgkd0t
IztnkpS89EFLN6cNBD+yWrs=
=umad
-END PGP SIGNATURE-
___
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] How to implement "customer groups" or "request groups"?

2007-12-17 Thread Steffen Poulsen

Hi,

We handle tickets from various companies in our request tracker, and
sometimes these companies ask for permission to share all tickets from
their company between themselves. A fair request I think :-)

I have put all users in a "CompanyGroup", but what rights should they be
given to be allowed to see each others tickets?

The tickets are distributed between multiple queues related to the
internal functions at our site, and they should _not_ be able to see all
the content of the queues - only the tickets created by staff in their
company.

I have searched the wiki and the mailing list, but have found nothing -
probably I am using the wrong search phrases. Any ideas or best
practices?

Best regards,

Steffen
___
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

AW: [rt-users] doesn't reply to requestor

2007-12-17 Thread Ruben Lehmann

Hi

 

Sorry for disturbing. Had a problem with some regex. Problem now solved.

 

Thx Ruben

 

Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Ruben
Lehmann
Gesendet: Montag, 17. Dezember 2007 11:21
An: rt-users@lists.bestpractical.com
Betreff: [rt-users] doesn't reply to requestor

 

Hi list

 

Got a ticket where the requestor's mail address is something like this.
[EMAIL PROTECTED]

Hi created a ticket in the queue "test"

 

Therefore [EMAIL PROTECTED] is listed as a watcher.

But when replying to the ticket this mail address isn't listed under "On
Correspond Notify Requestors and Ccs with template Correspondence"

There is just nothing. So no answer will be send.

 

Is it because the mail address contains the same word as the queues
name?

 

Thanks and regards

Ruben

 

 

___
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] doesn't reply to requestor

2007-12-17 Thread Ruben Lehmann

Hi list

 

Got a ticket where the requestor's mail address is something like this.
[EMAIL PROTECTED]

Hi created a ticket in the queue "test"

 

Therefore [EMAIL PROTECTED] is listed as a watcher.

But when replying to the ticket this mail address isn't listed under "On
Correspond Notify Requestors and Ccs with template Correspondence"

There is just nothing. So no answer will be send.

 

Is it because the mail address contains the same word as the queues
name?

 

Thanks and regards

Ruben

 

 

___
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

R: R: [rt-users] Having problems with a default install of 3.6.5

2007-12-17 Thread Gianluca Cecchi

I was only able to read your answer some minutes ago.. Next time please send 
messages to all the list, so that eventually other guys could give quicker 
replies...

The 'Configuration' link resolves to the same page as yours for me, so it 
doesn't seem a problem about rt itself.
When you have a link pointing to a directory, it defaults to some kind of page 
into that directory, tipically index.hmtl.
You define it inside apache configuration file (/etc/httpd/conf/httpd.conf on 
my fc6).

Pehaps your apache config is different form the default one...
The directive inside httpd.conf is DirectoryIndex and it is this one below for 
me:

# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents.  The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var

I have also this in my rt3.conf file (see in particular the "RedirectMatch" 
entry) under /etc/httpd/conf.d/. 
Don't know if could be another source of problems if misconfigured:

Alias /rt3 "/usr/share/rt3/html"

PerlModule Apache::DBI
PerlRequire /usr/sbin/webmux.pl


  AllowOverride All
  Options ExecCGI FollowSymLinks



  RewriteEngine On
  RedirectMatch permanent (.*)/$ $1/index.html
  AddDefaultCharset UTF-8
  SetHandler perl-script
  PerlHandler RT::Mason



> -Messaggio originale-
> Da: Mike Gracy [mailto:[EMAIL PROTECTED] 
> Inviato: venerdì 14 dicembre 2007 21.54
> A: Gianluca Cecchi
> Oggetto: Re: R: [rt-users] Having problems with a default 
> install of 3.6.5
> 
> Ok, I updated the logging path in RT_SiteConfig.pm and set up 
> the same dir below.  Logging works now.  Thanks.
> 
> I just discovered what is happening with the 'Configuration' link.
> It is resolving as 'rt./Admin/'.  It should 
> have 'index.html' on the end of it.  When I put the 
> 'index.html' on the end, it works perfectly.  Which file can 
> I edit to fix this?
___
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] wiki error? SetCorresponderAsCC

Re: [rt-users] How to implement "customer groups" or "request groups"?

RE: [rt-users] How to implement "customer groups" or "request groups"?

[rt-users] Not sure what is wrong with rt-mailgate

Re: [rt-users] Trouble after upgrade

Re: [rt-users] Trouble after upgrade

Re: [rt-users] Trouble after upgrade

Re: [rt-users] Having problems with a default install of 3.6.5

Re: [rt-users] Trouble after upgrade

Re: R: R: [rt-users] Having problems with a default install of 3.6.5

[rt-users] bounce handling -- rtbouncehandler download link or alternatives

Re: [rt-users] Trouble after upgrade

[rt-users] Create Ticket on Resolve, but only if Custom Field is....

[rt-users] How to implement "customer groups" or "request groups"?

AW: [rt-users] doesn't reply to requestor

[rt-users] doesn't reply to requestor

R: R: [rt-users] Having problems with a default install of 3.6.5

17 matches

Site Navigation

Mail list logo

Footer information