Hey,
i want the Unowned Tickets on the frontpage to be sorted by due, not
by created.
problem: if a ticket has no due set, it gets a higher rank than
tickets with a given due. if i set the search order to descending, the
tickets with a smaller due get a higher rank.
any solutions?
My database has grown huge because our clients seem to feel it is
important they us pictures to our ticket system. Although we have only
27K tickets, the database is 1.7 GB and the time to display a ticket has
become in excess of five seconds. I don't need any of these attachments,
is there I
Craig. Thanks for your answer.
I re run the migrate script (migrate-2.0-to-2.1) just to verify, and I
realice it is failing just before the importing articles (line 109), with
this error:
# perl -I/usr/lib/rt/ ./sbin/migrate-2.0-to-2.1
[Mon Nov 13 13:01:30 2006] [crit]:
Title: CustomFieldValues Table Question
I am looking at the RT database table for CustomFieldValues and I am wondering about the SortOrder field. I am trying to create a script that will automatically add potential values for some custom fields and I'm not sure what the SortOrder field
On Mon, Nov 13, 2006 at 09:31:23AM -0500, Rappaport, Evan wrote:
I am looking at the RT database table for CustomFieldValues and I am
wondering about the SortOrder field. I am trying to create a script
that will automatically add potential values for some custom fields and
I'm not sure
On Thursday 09 November 2006 22:10, Bill Weaver wrote:
When I try to reference that within a
Template like this:
To: {$Ticket-FirstCustomFieldValue('Email');}
It returns undef.
You want to do something like this instead:
To: {
my $email;
my $val =
When I use the interactive mode to enter a ticket via the cli (rt create -t
ticket) I have a text field option. I cannot seem to find this if I just want
to create a ticket from the clie, ie rt create -t ticket subject='test'
text='text test'
Carl
On Monday 13 November 2006 11:13, Bill Weaver wrote:
Thanks for the reply. I tried your suggestion below but the address
it ends up with is the [EMAIL PROTECTED] value so it still isn't
getting it from the custom field.
So we have established that the ticket does not have the custom field
Log 1 (Below) : When I login as a user who has a user with the same
userid
and password in RT and Windows Server 2003 active directory
It seems to find the entry but fails the LDAP authentication. The
error
message is in bold .
How were these RT accounts created ?
I found if the accounts
Hi Isaac
I did post a solution, but I'll reprint it here for completeness:
--Quote--
I found a solution to this myself! Thanks to everyone who provided possible
fixes. It's probably not elegant but it seems to fit ok.
The trick was in this post to RTIR
Hello,I've been trying to setup LDAP integration in RT 3.6.1, however I am unable to get authentication to work properly. Authentication against the LDAP directory succeeds (the code is able to bind with the supplied credentials), however the $UserObj-Id variable remains undefined, and the rest
When I try to use the example given to add a new ticket here is what happens:
[EMAIL PROTECTED] ~]$ rt create -t ticket subject='new ticket' priority=10 \
add [EMAIL PROTECTED]
rt: edit: Unrecognised argument 'subject=new ticket'.
The only way I can get a new ticket to be added is to leave
Thank you for the reply, seems like the only thing missing is the virtualhost for port 80. Since the old app was running on server root, we had not specified any virtualhost for that. Lets see, if this helps by putting it in a separate container.
Thanks again.Thanks and RegardsSujith EmmanuelOn
Basics:
We have a custom field called 'Profiles' which is a list of all our
customers. When a ticket is received, we add the customer profile to
the ticket. This allows us to keep track of work we've done for each
customer.
Requested:
We need to have in place something which my boss is calling
Tom Lanyon wrote:
Hi List,
We seem to be having issues with our production RT 3.6.1 instance when
using CustomFields. Everything works perfectly if we don't set a value
for a custom field, but as soon as you try to create a ticket with a
value for one of the custom fields we get a Ticket
15 matches
Mail list logo