PDA

View Full Version : Customize Settings Lost on Log Out

Carl@AWS
11-20-2007, 09:35 PM
We just upgraded from 3.6 to 4.0 yesterday and even though things are significantly different we like it better overall. Seems faster.

We're still trying to figure some things out and one that I ran across is that everytime I log in again my customized settings are gone and back to the default.

What am I doing wrong?

Also, what is the default sort order? and how which sort order should I use to view them in the order that they arrived in the HelpDesk?

Thanks

Carl
stephenb
11-20-2007, 09:54 PM
Are you using the Overview to view your tickets? The customize feature is only for that current logon. Once you log out, the columns will be reset. The only way to keep your settings is by using the My Workspaces to view your tickets.
Carl@AWS
11-20-2007, 10:35 PM
Are you using the Overview to view your tickets? The customize feature is only for that current logon. Once you log out, the columns will be reset. The only way to keep your settings is by using the My Workspaces to view your tickets.

Well that kind of sucks. :)

I was kind of liking the new boxes on the left so that I didn't have to duplicate my view from 3.6.
Carl@AWS
11-20-2007, 10:36 PM
Another issue:

Outbound messages are now including all of our internal e-mails addresses in the To: field. Previously it just had the requester.

How do we make it work this way again?
neenach2002
11-22-2007, 04:05 AM
Carl,

I suggest you try "Copy" and then use customize in the My Workspace area! :) It will save your changes there.
jstanden
11-27-2007, 12:03 AM
We can make the Overview preferences persist between logins, it just hadn't been high priority up to this point. But this is being requested very often (and that's a good thing for Overview as a feature, it means it's being used!).

Outbound messages are now including all of our internal e-mails addresses in the To: field. Previously it just had the requester.

The only reason I can see that happening is if your internal addresses are actual requesters on the tickets (along with the customers). This happens on migrations if the workers aren't set up with the same addresses before the tickets are imported.

The fix is pretty easy from the database. Just find the "address.id" for your people and remove those links from the "requester" table.

I added a knowledgebase article to explain this:
http://www.cerberusweb.com/kb/article/000036

Thanks!