Comment by
Trever F [14/Mar/08 02:22 PM]
Workspaces are completely useless to me unless this (or something like it) is implemented. I'm not going to spend the first week of my helpdesk deployment training users who have no experience with cerberus yet on how to create custom workspaces just to tell which tickets they've already closed.
Hmmm. Come to think of it, why's this not just part of the overview? Custom workspaces are great, but there seem to be a lot of standard views for helpdesk software that just aren't built into cerb4. I'd gladly trade custom workspaces for having these as simple drop-down views from the overview:
1. All my tickets, open or waiting.
2. All my closed tickets.
3. All tickets in a given group, open or waiting (Actually, just getting rid of "waiting" as a separate view would be a big improvement!).
4. All tickets available to me, over all groups.
I bet the first and second most frequently created workspaces in cerb4 are "closed tickets" and "all my tickets".
I don't even see any way to create a workspace showing all tickets "available to me" (meaning assigned to me or in my groups and assigned to no one).
extremely important!!!
Hmmm. Come to think of it, why's this not just part of the overview? Custom workspaces are great, but there seem to be a lot of standard views for helpdesk software that just aren't built into cerb4. I'd gladly trade custom workspaces for having these as simple drop-down views from the overview:
1. All my tickets, open or waiting.
2. All my closed tickets.
3. All tickets in a given group, open or waiting (Actually, just getting rid of "waiting" as a separate view would be a big improvement!).
4. All tickets available to me, over all groups.
Comment by
Joe Geck [23/Oct/08 09:27 PM]
Additional feedback from forums:
http://www.cerb4.com/forums/showpost.php?p=7160&postcount=1
I would like to be able to have shared workspaces such as
'tickets assigned to user x' or 'tickets relating to issue x' and share them with other members of the team and management without having to set up a specific workspace on their login.
If I could create a workspace, then perhaps check 'shared workspace' (or 'shared filter' )and ensure I could goto a URL like
http://cerberus-helpdesk.com/index.php/tickets?sharedworkspacefilter=bobs_tickets
I will though my two cents into this. In Cerb2 we had something kinda like this were we could create a view and share it with everyone. I created one that got used by 90% of the group because unlike the default it showed the fields we care most about. It would be nice is there was a option to do the same in cerb4
Thanks
Robert
Comment by
Joe Geck [29/Oct/09 12:56 PM]
Related:
CHD-308
Share worklist/workspace by copying from other workers
CHD-1483
[E-mail Notifications] Copy preset Watchers automatically to new workers
This week I had to spend several hours configuring the same workspace (consisting of the same 5 worklists) over and over for each of my workers. A way to create a workspace template and then copy it for a worker would save A LOT of time.
Comment by
Joe Geck [12/May/10 09:45 AM]
+1 "Is there a way that I can create a workspace for each worker and assign it to them?"
http://www.cerb4.com/forums/showpost.php?p=14352&postcount=1
For 5.6:
* [Workspaces] Shared workspaces have been implemented. This allows multiple workers to see the exact same worklists in a workspace. Workspaces can be owned by workers, groups (managers), or roles (admins). Editors can change the worklist (name/required filters/columns), and readers can have their own subtotals/paging/sorting. This ensures multiple workers have the same perspective. The owner of a workspace is displayed at the top of the tab (if not owned by the current worker). Changes to shared worklists will automatically syndicate to any workers using them.
* [Workspaces/Usability] Creating a workspace requires fewer steps now. Previously you had to create the workspace by name, then add it, click to its tab, and hit the Edit button. Now the 'Create Workspace' button will provided a popup for editing the workspace immediately.
Implemented in 5.6