[SOLVED] OrderBy not working in overview

[S1lv3rW1z4rd]

Hi,

Since the new release 6 my dashboard is sorted with oldest tickets on top.

I searched the admin settings to change this and ended up here;



But changing the SortBy field with either "Down" or "Up" doesn"t seem to change the order.
Am I missing something ?

Changes were successful deployed.

[root]

Hi,

What do you expect by sorting the queue by age, what should the result looks like?

- Roy

[jojo]

Wrong Sysconfig Setting

[S1lv3rW1z4rd]

Well default it now shows like this;



When I press at Age at the top of the column it shows in reverse order like



This is what I want it do by default.

When I refresh the oldest ticket is back at the top.

Which Sysconfig setting is wrong jojo ?

[root]

Hi,

The System Configuration you showed us (0270-TicketQueueOverview) does not match the screenshot (0120-TicketNew) of the result.

- Roy

[S1lv3rW1z4rd]

Hi Roy,

Yes I'm aware but ticketnew doesn't have a sort property?
Where should I configure it ?




I tried to add a Sort field and fill in the properties and deployed without error;
But still no change;

[root]

Hi,

Add SortBy and OrderBy to the Attributes parameter, separated by ;

- Roy

[S1lv3rW1z4rd]

Awesome !
That works, Thanks a lot for your quick reply !

[marcelwuestner]

I also have this problem and the solution from roy works for me as well.

But after the automated reload from the system, the tickets are sort by age with the oldest tickets on top.

What should I do?

[S1lv3rW1z4rd]

Hi Marcel,

Good question I also have this behavior.
After a refresh the newest is back on top but this is kind of annoying indeed.
I haven't found the solution yet.

[Drak0]

same problem here, after automatic refresh the oldest ticket is on top

[S1lv3rW1z4rd]

Does anyone know the solution ?

I would expect it to be this setting here but the sort is already set at Down instead of Up;

[zzz]

Hello,

this could/should be fixed in the upcoming 6.0.4.

Best regards

[S1lv3rW1z4rd]

Thanks, I see in the release notes of 6.0.4 this is indeed fixed.
Will update soon.

[S1lv3rW1z4rd]

I can confirm the update to 6.0.4 fixes the issue.