Hi David,
thank you for the advice. I will try this.
Wolfgang
Am 2012-04-17 14:55, schrieb David Heidt:
> Hi Wolfgang,
>
> I think upgrading directly to 2.3 (2.3.6) makes more sense. See the
> UPGRADING -File of Version 2.3.6:
>
>
> These instructions are for people upgrading OTRS from "2.2"
Hi Wolfgang,
I think upgrading directly to 2.3 (2.3.6) makes more sense. See the
UPGRADING -File of Version 2.3.6:
These instructions are for people upgrading OTRS from "2.2" to "2.3".
Upgrades from Versions 2.x to 2.(x+1) are imho supported, perhaps this
solves your problem.
For your o
It's not something that can easily be diagnosed on a "user" group, your
setup seems to be very specific.
Although not free, in your situation it might be worth contacting OTRS
support.
Steve
On 17 April 2012 13:11, Wolfgang wrote:
> So i guess that no one has an idea how to fix this?
>
> Wolf
So i guess that no one has an idea how to fix this?
Wolfgang
Am 2012-04-03 14:25, schrieb Wolfgang:
> Hello,
>
> i am still using otrs 2.2.7 and want to upgrade to 3.1.
> I just tried to upgrade to 2.2.8 but after the upgrade the following
> happens:
>
> i do have many companies/customers. a
Hello,
i am still using otrs 2.2.7 and want to upgrade to 3.1.
I just tried to upgrade to 2.2.8 but after the upgrade the following
happens:
i do have many companies/customers. and each has it's own queue and own
system-address. when i login as a customer of company1 and create a
ticket, this cu
