Re: [rt-users] Custom Field validation extension

[Peter Viskup]

Discovered the issue.
The CF Validation string is saved as attribute within the CF
creation/modification. The CF's Validation string showed the old
version of that regexp.
Thus once the CFValidation string is changed, the CF itself (using
this validation string needs) to be assigned with the new string using
the Admin/CF/Modify interface.

-- 
Peter Viskup

On Mon, Jun 13, 2016 at 11:13 AM, Peter Viskup  wrote:
> Hello all,
> just extended the CFValidations in
> /opt/rt4/local/html/Admin/CustomFields/Modify.html by
> '(?#Version)^[0-9._\-]+$',
> '(?#Optional Version)^([0-9._\-]+)?$',
>
> Unfortunately the CF input still does not accept string "8.15-1" and
> report "Broken in: Input must match [Optional Version]".
> The Mason cache was cleaned prior the ticket creation.
> Am I doing something wrong?
>
> --
> Peter Viskup
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016

[rt-users] Custom Field validation extension

[Peter Viskup]

Hello all,
just extended the CFValidations in
/opt/rt4/local/html/Admin/CustomFields/Modify.html by
'(?#Version)^[0-9._\-]+$',
'(?#Optional Version)^([0-9._\-]+)?$',

Unfortunately the CF input still does not accept string "8.15-1" and
report "Broken in: Input must match [Optional Version]".
The Mason cache was cleaned prior the ticket creation.
Am I doing something wrong?

-- 
Peter Viskup
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016

Re: [rt-users] Any way to speed up shredding?

[Robert Waldner]

On 06/10/2016 01:03 PM, Christian Loos wrote:
> Am 10.06.2016 um 12:02 schrieb Robert Waldner:
>> I'm trying to get rid of old crud (deleted and rejected tickets, mostly
>> spam) in our RT-DB, and so use rt-shredder. Which seems to work fine,
>> but is so slow that my best estimate for it to finish wiping ~80k
>> tickets is "upwards of 6 months":
>>
>> time ( rt-shredder --force --plugin "Tickets=query,(status = 'rejected'
>> OR status = 'deleted') AND id <61;limit,10")
>>
>> real9m33.764s
>> user0m6.984s
>> sys 0m0.708s
>>
>> Any hints on possibilities to speed this up?
>>
>> (rt-shredder from RT 3.8 (Debian), incl. RT-IR 2.4, postgres backend)

> There are some database indexes suggested:
> https://docs.bestpractical.com/rt/4.4.1/RT/Shredder.html#Database-Indexes
> 
> I use just some if them, es they improve shredding tickets enough for me:
> CREATE INDEX SHREDDER_CGM3 ON CachedGroupMembers (Via, Id);
> CREATE UNIQUE INDEX SHREDDER_GM1 ON GroupMembers(MemberId, GroupId);
> CREATE INDEX SHREDDER_TXN3 ON Transactions(TYPE, OldValue);
> CREATE INDEX SHREDDER_TXN4 ON Transactions(TYPE, NewValue);

Thanks for the tip - sadly, it doesn't help (it's still nearly 1
minute/ticket deleted).

Kind regards,
robert
-- 
// CERT Austria - Robert Waldner 
// http://www.cert.at/ - T: +43 1 5056416 78
// Eine Initiative der nic.at GmbH
// http://www.nic.at/ - Firmenbuchnummer 172568b, LG Salzburg



signature.asc
Description: OpenPGP digital signature
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016