dthao

 @"joeybrown" Is there a reason we have to pick and choose? Why can’t all custom fields that can be sorted, filtered, or searched be available for these functions?

Let me give you an example and see if you still think a ticket is needed. We have these specific fields that should only be filled out by an agent: Vendor Name Escalation Date Case Number This is used when an agent has to escalate an issue to a vendor. These fields are hidden from the requester. When an agent submits a…

This is a problem when you try to @ mention a user in the comment section also. Users with the same name will show but there is no way to know who is who and you can't view the email address like you can when you add the user in the CC field.

Or allow admins to control this and decide which is the default for their organization.

Agree, if that is possible, that would be fine also.

I just submitted a case on how to disable the 'modify forms after submission' as it negatively impacts our approval process. It was in labs and we had control of who had permission to use this but now it's no longer in labs and feature is available to all agents. We'd like this disabled also.

Agree. Our Service Catalog items default to 'Popular' and we would like it defaulted to 'Aphabetic' but there is no setting in Setup to control this.

Completely agree about allowing custom fields that store values from other integrations to be used in the incident forms or service catalog and have those values auto-populate like the 'Site' and 'Department' fields.

Here's my case number 01605445. I just heard back from support that there's no way to disable it and to submit a new feature request. I'm happy to do so if needed. Please let me know. Thank you.

That's odd that this is happening to you because ours auto-populates. We sync our users in from our SSO platform. When users submit an incident ticket or service request from the catalog, their site and department auto-populates. We don't have the option to hide these fields.

We are using O365 but have a spam filter that receives the messages first and then forwards to O365. The messages in the spam filter shows the odd characters also. Since I've resolved this by removing the extra spaces from the notification templates I'll wait to see if this happens with another 3rd party, if so, then I'll…

We got the same response from Solarwinds support hence why I'm researching here to see if others have experienced this. We did test with a Solarwinds email account and the account received the email just fine so they are saying it's our mail server. We're not experiencing this with any other emails though. Only emails from…

Hi, Was this ever resolved? We're having a similar issue with our email notifications from Service Desk except the odd character is a question mark inside a diamond. Thanks.