I have just found what appears to be a solution for this problem enabling
the UseSQLForACLChecks in your RT_SiteConfig.pm . Once I enabled this the
unowned search now displays only tickets that the user has permission to see
and any searches you run in simple search will return a result that matche
Thanks for your reply Bill
I think I hadn't noticed this "feature" before because I only had a couple
of people using it but had just added a new user who forwarded a large
number of emails to her queue in rt so that when I next looked at my default
RT page my unowned tickets had disappeared. I di
Howdy John,
>From my understanding this is a "feature" of RT, There isn't much one can
do about it, the settings aren't granular enough to cover what a single user
has the right to see, high up on my wish list is something along the lines
of what you are looking for, I would love to be able to li
Hi
I am having a problem where the unowned search is not restricting its
results to only tickets that are in queues the user has the see ticket
permission for. This is causing the unowned ticket list to not display any
tickets in the rt at a glance page if another queue has 10 more recent
unowned
Jamie,
This can be set up. Create a new Notification script the Notifies
Owner on whatever and that will take care of them getting email on the
tickets they own. However, you mentioned something about co-owned
tickets. TO my knowledge, RT allows only 1 user to be a ticket owner.
That data
Matt Simerson wrote:
> If perl isn't your cup of tea, write your web app in your favorite
> language and interface directly with the database. You'll have a bit
> more testing to do during future RT upgrades, but the RT schema is
> quite stable.
Actually, you're forgetting about the ruby lib
On Mon, 11 May 2009 19:39:50 -0700 (PDT), "kenadams2"
said:
> I have just finished setting up RT and have a small problems with the way
> the users are setup. We have 35 users. 30 of them are remote. Each user
> has a queue so that tickets can be lodged to them. They all have create
> ticket privs
Hi list,
I've programmed my own action module to create tickets from
forwarded mails.
Therefore I scan from and subject headers in all attachments
and set the ticket's requestor to the original mail from and the
subject to the original subject.
Now I would like to also set the tickets content to
On May 12, 2009, at 11:11 AM, eric_malenf...@mitel.com wrote:
> Well, I don't need to implement this style anymore - provided some
> reasoning, and was agreed upon.
> What I would like to do, is now to increase the baseline of the
> ticket # - I don't need to start @ 1- too low, so I want to
Well, I don't need to implement this style anymore - provided some
reasoning, and was agreed upon.
What I would like to do, is now to increase the baseline of the ticket # -
I don't need to start @ 1- too low, so I want to start around 1000.
Any idea how I can increase this number?
Eric Malenf
Tue 12 May 2009 13:49:03 GMT
David Hobley wrote:
> Ruslan,
>
> thanks for your reply - how can I check this from the UI exactly? Given
> I can't login!
Local accounts can always login. Login as root to check the configuration.
>
> I have the following in my RT_SiteConfig.pm, so I thought I had
Ruslan,
thanks for your reply - how can I check this from the UI exactly? Given I can't
login!
I have the following in my RT_SiteConfig.pm, so I thought I had it all
configured:
Set($ExternalAuthPriority, [ 'Primary_LDAP' ]);
Set($ExternalInfoPriority, [ 'Primary_LDAP' ]);
Set($ExternalSe
Well, modifying the code is what was done years ago for our current
implementation. It was deployed back before Mitel had purchased E-Smith
(old Linux distro) and
is actually still in use today, but we have some new requirements which
warrants an upgrade.
The one thing that would be great to ke
Hi all,
I'm currently implementing RT in our department at work and I
currently have the sysadmin team as AdminCc's for all relevant queues.
However, some members of the team do not want to be notified of
correspondence or comments for tickets which they do not own - but
still want notifications a
This often indicates that you havn't enabled the extension. Or
installed incorrectly. If you're on RT 3.8.2 then can check system
configuration via UI, especially Plugins option and loaded modules.
On Tue, May 12, 2009 at 12:12 PM, David Hobley
wrote:
> All,
>
> I am trying to integrate RT::Authe
All,
I am trying to integrate RT::Authen:: ExternalAuth to my RT instance and it is
not letting me log in. I have configured debugging in my RT_SiteConfig.pm:
Set($LogToFile, 'debug');
Set($LogDir, '/var/log/rt');
but the only message I get indicating problems is a FAILED LOGIN error in the
16 matches
Mail list logo
