>> We have been happily using OTRS 1.3.1 on Suse 9 since 2005 and it has
>> been working flawlessly (I know v1.3.1 is very old but works the way
we
>> want it so there has never been an incentive to upgrade!) .
>>
>> A feature we use is FreeText fields which we pre-fill using an sql
>> statement i
paul.mcilfatr...@bt.com wrote:
>
> We have been happily using OTRS 1.3.1 on Suse 9 since 2005 and it has
> been working flawlessly (I know v1.3.1 is very old but works the way we
> want it so there has never been an incentive to upgrade!) .
>
> A feature we use is FreeText fields which we pre-fil
> We have been happily using OTRS 1.3.1 on Suse 9 since 2005 and it has
> been working flawlessly (I know v1.3.1 is very old but works the way
> we want it so there has never been an incentive to upgrade!) .
>
> A feature we use is FreeText fields which we pre-fill using an sql
> statement in a P
We have been happily using OTRS 1.3.1 since 2005 and it has been working
flawlessly ever since (I know v1.3.1 is very old but it just works!) .
A feature we use is FreeText fields which we fill using a sql statement
in a Perl script which is run when a ticket is automatically moved to a
certain qu
