-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
example use cases
- Associate existing tickets and tickets that come through email or various other sources with a Service Desk (when the Customer Request Type field isn't filled in, tickets won't be displayed in the Customer Portal).
- Move tickets between Service Desks (triage).
- Create and move tickets on customers' behalf, e.g. after a phone call.
- is related to
-
JSDSERVER-55 Issues created before Service Desk will not show in the user's portal
- Closed
-
JSDSERVER-193 Customer Request Type in Basic Search
- Gathering Interest
-
QUALITY-266 Failed to load
- relates to
-
JSDSERVER-38 As an admin I want Service Desk to recognise issues created by Mail Handlers and through the standard Create Issue
-
- Closed
-
-
JSDCLOUD-42 Allow "Customer Request Type" to be manually edited
- Closed
-
JSDSERVER-24 As a service desk customer, I would like to have the ability to have an "email based" workflow for the users that don't want to go to the portal
- Closed
- supersedes
-
JSDSERVER-281 Changing Issue Type does not update the Customer Request Type
-
- Closed
-
Form Name |
---|
[JSDSERVER-42] Allow "Customer Request Type" to be manually edited
Resolution | Original: Done [ 17 ] | New: Fixed [ 1 ] |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3012143 ] | New: JAC Suggestion Workflow 3 [ 3647178 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665928 ] | New: JAC Suggestion Workflow [ 3012143 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2323351 ] | New: Confluence Workflow - Public Facing v4 [ 2665928 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JSD Suggestion Workflow [ 2052127 ] | New: JSD Suggestion Workflow - TEMP [ 2323351 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2047599 ] | New: JSD Suggestion Workflow [ 2052127 ] |
Workflow | Original: JSD Suggestion Workflow [ 1279496 ] | New: JSD Suggestion Workflow - TEMP [ 2047599 ] |
Description |
Original:
h5.example use cases
- Associate existing tickets and tickets that come through email or various other sources with a Service Desk (when the Customer Request Type field isn't filled in, tickets won't be displayed in the Customer Portal). - Move tickets between Service Desks (triage). - Create and move tickets on customers' behalf, e.g. after a phone call. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-42]. {panel} h5.example use cases - Associate existing tickets and tickets that come through email or various other sources with a Service Desk (when the Customer Request Type field isn't filled in, tickets won't be displayed in the Customer Portal). - Move tickets between Service Desks (triage). - Create and move tickets on customers' behalf, e.g. after a phone call. |
Link |
New:
This issue relates to |
Labels | Original: affects-cloud vc | New: affects-cloud affects-server vc |