Re: [rt-users] default format of quick search
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Friday, August 03, 2012 8:55 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] default format of quick search
On Thu, Aug 02, 2012 at 11:20:31AM -0500, Josh Hopkins wrote:
>Is there somewhere to change the default format of the quick search for
> all users?
Do you mean the Simple Search in the upper right corner of RT which you could
change with the DefaultSearchResultFormat config option or do you mean the
Queue/ticket listing on the homepage? You'd need to tell us about what you
want to change.
-kevin
-End--Original--Message-
I am using RT 4.06. I did find a few ways to edit the build in searches by
trying to edit them and then clicking on the link above that would say
something like edit original search "search name". But I am mostly trying to
change the look of the results that come back from the quick search widget that
is located on the right by default.Where do I find the
DefaultSearchResultsFormat config option?
What are are trying to have would be something like?
' __id__/TITLE:#',
'__CustomField.{ClientOrganization}__',
'__Status__',
'__Subject__/TITLE:Subject',
'__QueueName__',
'__TimeWorked__',
'__LastUpdatedBy__',
'__NEWLINE__',
'',
'__Requestors__',
'__OwnerName__',
'__NBSP__',
'__CreatedRelative__',
'__CustomField.{TimeWorkedOverride}__',
'__LastUpdatedRelative__'
Does the DefaultSearchResultsFormat config options also contain the default
sort options? Is there also a way to remove user customizations that have been
made to the formatting to see the new formatting? Thanks,
/Josh
Re: [rt-users] Unable to use NotifyGroup with rt-crontool
On 08/03/2012 02:23 AM, Shrivallabh Deshmukh wrote: > I checked to see that the group is getting loaded correctly. But it is > not able to get hold of a transactionObk it seems like. > > That makes sense since there is no transaction that has occured. Rather > this is a cronjob which is triggering the action. Some actions and conditions require a transaction. See `perldoc bin/rt-crontool` for how to specify one.
Re: [rt-users] Missing icon
Quite strange: I removed autohandler file, restarted apache2, and the problem still happened. Then restored autohandler file again, and now the problem looks solved. Can't understand the reason, but... Thank you very much.
Re: [rt-users] default format of quick search
On Thu, Aug 02, 2012 at 11:20:31AM -0500, Josh Hopkins wrote: >Is there somewhere to change the default format of the quick search for > all users? Do you mean the Simple Search in the upper right corner of RT which you could change with the DefaultSearchResultFormat config option or do you mean the Queue/ticket listing on the homepage? You'd need to tell us about what you want to change. -kevin pgpEVbpLEvPpy.pgp Description: PGP signature
Re: [rt-users] fresh install of RT-4.0.6 which JSON to use
To answer my own question. It looks like by taking the default 'Y' to the CPAN prompt:- Do you want to install JSON::XS?(Y/n) [Y] that both JSON modules were installed. JSON -- 2.53 JSON::XS -- 2.33 -- On Thu, 2 Aug 2012, o.n...@cs.ucc.ie wrote: Hi all, I am building a new install of RT-4.0.6 while going through the perl modules needed I get a choice when selecting a version of JSON. here is the message from the command perl -MCPAN -e 'install JSON' CPAN.pm: Going to build M/MA/MAKAMAKA/JSON-2.53.tar.gz Welcome to JSON (v.2.53) = If you install JSON::XS v.2.27, it makes JSON faster. ** CAUTION ** * This is 'JSON version 2' and there are many differences * * to version 1.xx * * Please check your applications useing old version.* * See to 'INCOMPATIBLE CHANGES TO OLD VERSION' and 'TIPS' * * Do you want to install JSON::XS?(Y/n) [Y] - My question is should I take the new version JSON::XS as offered? -- Oliver Nash CSSG Computer Science UCC - -- Oliver Nash CSSG Computer Science UCC -
Re: [rt-users] Missing icon
Am 31.07.2012 18:15, schrieb Jose M Vidal: Hi, After installing JSGantt plugin (not sure if there's any relationship though) there's something missing in the ticket's page (//mydomain/rt/Ticket/Display.html?id=nn) The link this icon is pointing is //mydomain/rt/Helpers/Toggle/TicketBookmark?id=nn If clicking in the missing icon, a stared icon appears, as shown in the screenshot. If I click again into the yellow star, it simply dissapears. Any clues? Thanks! The problem is caused by the Mason-Handler. It doesn't bypass the icon file. I have faced the same problem a few days ago too. Check if there is an autohandler or dhandler file in local/html/NoAuth/images and test what happens when you remove them. I don't recall how I fixed it, but in the end I remove these files from there and it worked. Remember to restart your http-server after the change. The icon file, btw, is share/html/NoAuth/images/empty_star.gif -- Mit freundlichen Grüßen/ Sincerely yours Alexander Reinzsch IT-software engineer NetSystem Netzwerk- und Systemtechnik GmbH
Re: [rt-users] Unable to use NotifyGroup with rt-crontool
i also had same issue some time ago and solved it like this:
$CRONTOOL --search RT::Search::ActiveTicketsInQueue --search-arg $QUEUE
--condition RT::Condition::UnownedTicket --condition-arg $PERIOD --action
RT::Action::Notify --action-arg $EMAIL --transaction first --template
$TEMPLATE
Notify and notifyGroup seems to work similar. i had an alias on mail server
for specific group, so it was acceptable for me to send one message to this
alias.
but key thing is to use --transaction [first | last | all] to show what
transaction you want to process.
On Fri, Aug 3, 2012 at 11:23 AM, Shrivallabh Deshmukh <
shrivallabh.deshm...@sungard.com> wrote:
> Folks,
>
> I am unable to use the rt-crontool with NotifyGroup action
>
> This is what I am running
>
> /opt/rt4/bin/rt-crontool --search RT::Search::ActiveTicketsInQueue
> --search-arg QueueName --condition RT::Condition::Overdue --action
> RT::Action::NotifyGroup --action-arg GroupName
>
>
> And this is the error I get
>
> [Fri Aug 3 09:03:43 2012] [critical]: Can't call method "CreatorObj" on
> an undefined value at /opt/rt4/bin/../lib/RT/Action/NotifyGroup.pm line 87.
> (/opt/rt4/bin/../lib/RT.pm:341)
>
> This is the function that is failing
>
> sub SetRecipients {
> my $self = shift;
>
> my $arg = $self->Argument;
> foreach( $self->__SplitArg( $arg ) ) {
> $self->_HandleArgument( $_ );
> }
>
> my $creatorObj = $self->TransactionObj->CreatorObj;
> my $creator = $creatorObj->EmailAddress();
>
> my $TransactionCurrentUser = RT::CurrentUser->new;
> $TransactionCurrentUser->LoadByName($creatorObj->Name);
>
> unless (RT->Config->Get('NotifyActor',$TransactionCurrentUser)) {
> @{ $self->{'To'} } = grep ( !/^\Q$creator\E$/, @{ $self->{'To'} }
> );
> }
>
> $self->{'seen_ueas'} = {};
>
> return 1;
> }
>
> And the line that is failing is my $creatorObj =
> $self->TransactionObj->CreatorObj;
>
>
> I checked to see that the group is getting loaded correctly. But it is not
> able to get hold of a transactionObk it seems like.
>
> That makes sense since there is no transaction that has occured. Rather
> this is a cronjob which is triggering the action.
>
>
>
>
>
--
Jack Zabolotnyi
Arces Network, LLC
e: jzabolot...@arces.net
w: http://www.arces.net
PGP key: 2048R/7F2AB658 2012-07-02
PGP fingerprint: 4C7E 00A8 5210 F3D9 0509 C70E 87C8 666E 7F2A B658
[rt-users] Unable to use NotifyGroup with rt-crontool
Folks,
I am unable to use the rt-crontool with NotifyGroup action
This is what I am running
/opt/rt4/bin/rt-crontool --search RT::Search::ActiveTicketsInQueue
--search-arg QueueName --condition RT::Condition::Overdue --action
RT::Action::NotifyGroup --action-arg GroupName
And this is the error I get
[Fri Aug 3 09:03:43 2012] [critical]: Can't call method "CreatorObj" on an
undefined value at /opt/rt4/bin/../lib/RT/Action/NotifyGroup.pm line 87.
(/opt/rt4/bin/../lib/RT.pm:341)
This is the function that is failing
sub SetRecipients {
my $self = shift;
my $arg = $self->Argument;
foreach( $self->__SplitArg( $arg ) ) {
$self->_HandleArgument( $_ );
}
my $creatorObj = $self->TransactionObj->CreatorObj;
my $creator = $creatorObj->EmailAddress();
my $TransactionCurrentUser = RT::CurrentUser->new;
$TransactionCurrentUser->LoadByName($creatorObj->Name);
unless (RT->Config->Get('NotifyActor',$TransactionCurrentUser)) {
@{ $self->{'To'} } = grep ( !/^\Q$creator\E$/, @{ $self->{'To'} } );
}
$self->{'seen_ueas'} = {};
return 1;
}
And the line that is failing is my $creatorObj =
$self->TransactionObj->CreatorObj;
I checked to see that the group is getting loaded correctly. But it is not
able to get hold of a transactionObk it seems like.
That makes sense since there is no transaction that has occured. Rather
this is a cronjob which is triggering the action.
