You can change the following ticket attributes using email messages if the value of the ticket field is set to User Modify.
For information on changing ticket field permissions, see Using ticket approvers.
A comma-separated list of email addresses or distribution lists. | |
A due date. The date can be in any format. For example, 4/3/2014, April 3, 2014, or next Thursday. | |
The submitter's username, full name, or email address. The email address is used for the username and email address fields. The full name is set to the Name portion of the email address. For example, name@domain.com. | |
The state of the ticket approval process. You can set this field to one of the following values: Approved, Rejected, None, or More Information Needed. | |
Indicates if only owners can comment on the ticket through email. When set to 1, the flag is True. Any other numeric value sets this indicator to False. | |
The value of a custom ticket field, where <number> is the custom field ID. For example, $custom_2=ABC assigns the value of ABC to the CUSTOM_2 ticket field. |
Approvers can change the following approval fields:
Modify the ticket. Use one of the following: Approved, Rejected, None, or More Information Needed. | |
Change the ticket approver. Enter a username from the ticket approval label. For instructions on setting up the label of approvers, see Using ticket approvers. | |
You can set custom fields for Service Desk tickets through email using the prescribed syntax.
The syntax takes the form @custom_fieldname=newvalue.
Custom fields cannot contain spaces. Use an underscore between words. For example, new_value.
Approvers can change the following approval fields:
Modify the ticket. Use one of the following: Approved, Rejected, None, or More Information Needed. | |
Change the ticket approver. Enter a username from the ticket approval label. For instructions on setting up the label of approvers, see Using ticket approvers. | |
You can set custom fields for Service Desk tickets through email using the prescribed syntax.
The syntax takes the form @custom_fieldname=newvalue.
Custom fields cannot contain spaces. Use an underscore between words. For example, new_value.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center