Feature Request - Auto refresh Overview and/or My Workspaces

[PerDellrup]

As the title show it would be nice to have a auto refresh as in the old Cerberus 3 to decrease double taking of tickets and so on.

[mfogg]

We considered this awhile back but decided against it because of the performance implications when many users leave a window constantly refreshing the server. The issue is located at http://wgmdev.com/jira/browse/CHD-31 if you want to read a little more information about it, or add your own comment.

[PerDellrup]

I can see that there could be performens issues with large companies with a slow server, but for all the others? What Im saying is that it might be an option for the administrator to turn on or off so that those that experiencing performans issues can turn it of, and maybe have it to default off.

Offtopic; the Payed licence of the forum is it open for questions like this and bugs? Or is it just support?

[Hildy]

It's more intended for things that don't work right, rather than feature requests, but you could use it for that if you wanted to.

[mfogg]

There's some merit to what you say. I've gone ahead and reopened the issue ( http://wgmdev.com/jira/browse/CHD-31 ) so we can at least take another look at it. It's not the most popular request right now though, so there's no guarantee we don't decide to pass on it again.

[hxc]

At the very least, there should be an automated notification system of some type...

I'm certain there are many companies like us, who use Cerberus in lieu of all other mail clients. We've had to resort to forwarding watcher emails to separate accounts for each worker, just so they can be notified by Outlook when a new ticket comes in to the helpdesk. I just don't accept the performance argument you guys keep pitching. It's far more efficient to let the web service manage a browser refresh than it is for a mail server to handle multiple watcher requests. Don't you agree?

[mfogg]

The browser probably isn't the greatest notification system at this time.

As you note Cerberus supports email notifications, but it also supports RSS notifications on any ticket list. You can use any 3rd party RSS application that supports notifications and subscribe to those feeds to tap into a better notification system than the browser can realistically offer (like systray notification).

It would also save the trouble of creating separate email accounts for forwarding, and assuage the performance hit from sending out numerous email notifications.

That said, I can see the argument for wanting to have some confidence that a ticket list you see on your screen is reasonably up to date without having to hit "refresh" like a paranoid monkey.

[hxc]

Very nice. I had everyone download and install the free Tristana RSS reader, which is one of the few free readers that support systray notification, then removed all the eMail notifications. Works like a charm. Thanks Mike!

[zaaj]

The browser probably isn't the greatest notification system at this time.

As you note Cerberus supports email notifications, but it also supports RSS notifications on any ticket list. You can use any 3rd party RSS application that supports notifications and subscribe to those feeds to tap into a better notification system than the browser can realistically offer (like systray notification).
.

Don't RSS feeds work by a reader parsing the results of a URL? Why can't Cerb4 check the RSS URL to see if the current view needs to be refreshed? I'm thinking AJAX type automated background checks of the RSS feed of course, so a full screen refresh is not done until needed...

[PerDellrup]

I did a temporary solution that seems to work. In file cerb4/plugins/cerberusweb.core/templates/tickets/ticket_view.tpl.php

FIND:
{if $view->id=='overview_all'}{*Only on Overview*}

AFTER ADD:
<SCRIPT LANGUAGE="JavaScript">
setInterval ("genericAjaxGet('view{$view->id}','c=internal&a=viewRefresh&id={$view->id}')", 59000);
</SCRIPT>


Set 59000 to what liking, it is how often the refresh should take place in milliseconds.