new Queue in admin area invisible

[yellowfish]

Hi,

I'm using OTRS 3.1.11, and have a few Queues defined in the admin area, Queu settings -> manage Queues.
Since a week I have activated the ITSM core, General catalogue and ITSM incident/problem management (3.1.10).

After that I tried to add a new queue in the admin area.
Something very weird is happening then, because the new Queue is not visible in the 'Manage Queues'.
When I look directly into the database und 'queue', the new Queue is there.
The auto increment value is sequential, which means that it's +1 compared to the last visible Queue seen from the GUI (there is no gap in the database)

When I login as a normal agent, I can pick the Queue to put the ticket in there.

Why is the new Queue not visible in the admin area?
Any help would be highly appreciated.

[yellowfish]

anyone?

[reneeb]

Delete Browsercaches?

[yellowfish]

Doesn't help, the issue appears on several browsers on different times (chrome, FF, IE).

[crythias]

List is from Kernel/System/Queue.pm sub QueueList
First it checks Queue Cache. If it exists, return it.

Kernel/Modules/AdminQueue.pm lists *any* queue (Valid => 0) (validity check, so it will show invalid queues, too)
SELECT id, name, FROM queue

nothing special.
bin/otrs.DeleteCache.pl

[jojo]

update to the latest patch level of your OTRS version.

[yellowfish]

Thnx for the updates.

List is from Kernel/System/Queue.pm sub QueueList
First it checks Queue Cache. If it exists, return it.

Kernel/Modules/AdminQueue.pm lists *any* queue (Valid => 0) (validity check, so it will show invalid queues, too)
SELECT id, name, FROM queue

nothing special.
bin/otrs.DeleteCache.pl

What do you mean with this? Do you want me to run the script DeleteCache.pl?

update to the latest patch level of your OTRS version.

Will this solve the issue? Upgrading to the latest version will take quite a bit of testing before implementation in the live environment...

[reneeb]

Did you check the OTRS log?

[jojo]

check the CHANGES file of the latest patchlevel. You should always update to the latest patchlevel. Your version already has some security bugs which are fixed in newer versions

[yellowfish]

Yes, the OTRS log doesn't help me.

But... it seems I just solved it.
I ran bin/otrs.DeleteCache.pl

And now the new entered queue is visible in the admin area.

How is this possible?

[jojo]

it is a known bug in your version, that the cache is not rebuilded on addinq Queues

[yellowfish]

Alright, thanks all for your help!