"Bugs" require a formal ticket.  You can log these via mysupport.symantec.com to save time - don't expect a quick response (if I don't follow-up, I can often wait over a week without response).

Having said that, with ServiceDesk I find that regardless of how obvious something is as a bug, you will almost always get the answer that it is working "as designed" and if you feel it should work differently it is not a bug but a "feature request" (https://www-secure.symantec.com/connect/articles/servicedesk-71-send-email-only-updates-case-if-sender-administrator is a good example of this where I opened a support case, was told "working as designed," complained and escalated and managed to get a fix... though, you'll notice in the linked article the support engineer opens still claiming this obvious bug is working "as designed").  The stated mechanism these days for making "feature requests" is by creating an "Idea" here on the Connect site.  Yes, even if you open a support case for your bug, if they can blow you off with the "feature request" line, the issue will never be reported to development.

Joe

That's what I thought but some things really are bugs or just silly UI decisions that should be changed. One example is that the support documents claim bowser independence and yet the developers chose to use labels as buttons on many forms. Safari and Firefox don't really like using those so most "buttons" don't work. This leaves me hunting down and editing each of these to replace the labels with real buttons to make them work.

Another example is inside subtasks. If you try to assign a subtasks in Safari then click ok to go back to the page before, the entire window closes so you can't do subtasks in that browser at all.

These aren't really product halting bugs but are things that should be fixed. I guess I will just have to open more support tickets of that's the only solution.