QueueMetrics > Running QueueMetrics

Custom reports - data/time order not consistent before 10am?

(1/2) > >>

scooby2:
When running custom reports the date/time is not in a consistent order for calls before 10am.

I am running version 1.4.7.1. Has this been fixed in a newer version?

Thank you,
Scooby2

example from today:
01/19 - 7:01:22
01/19 - 7:08:50
01/19 - 7:05:59
01/19 - 7:09:19
01/19 - 7:17:16
01/19 - 7:24:52
01/19 - 7:21:14
01/19 - 7:19:26
01/19 - 7:37:58
01/19 - 7:42:07
01/19 - 7:40:03
01/19 - 7:43:45
01/19 - 7:46:58
01/19 - 7:49:14
01/19 - 7:55:09
......
01/19 - 9:54:22
01/19 - 9:51:06
01/19 - 9:59:40
01/19 - 9:59:37
01/19 - 9:59:49
01/19 - 10:00:10
01/19 - 10:03:42
01/19 - 10:04:39
01/19 - 10:04:50
01/19 - 10:04:53
01/19 - 10:05:18
01/19 - 10:06:09
01/19 - 10:06:57
01/19 - 10:08:14
01/19 - 10:09:23
01/19 - 10:09:40
01/19 - 10:09:44

QueueMetrics:
Actually I don't think it's atime error, but the fact that QM natively stores calls in the order they are hung up, so this si the native showing mode. You should be able to sort them any way you like anyway.

scooby2:
Sorry, I did not explain myself very well. When you click on Date to sort the calls by time, it sorts everything >= 10am properly. Everything before 10am does not sort in numerical order. This is confirmed on Mac Firefox and Linux Firefox. Can you see if you can reproduce this? Just make sure to have calls earlier than 10am.

Thank you,
Scooby2

QueueMetrics:
Yes - likely it's because they are sorted as strings.
This could be addressed by changing the date format in the language files, so that 9:45 AM gets to be 09:45 AM.
We are tracking this as bug #615.

scooby2:
Thank you!

Navigation

[0] Message Index

[#] Next page