Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3182

I want to be able to set the "Customer Request Type" manually when raising Service Desk ticket outside of Portal

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Currently, when raising an issue via the portal, the "Customer Request Type" is set automatically according to the type of issue created via the portal.

      When viewing an issue created this way, the Service Desk request section shows:
      Request Type: Service Request (for example)
      Customer Status: Open (for example)
      Channel: Portal

      However, if a Service Desk Agent logs the request via the normal Jira interface, this is not set.

      When viewing an issue created via Jira interface the Service Desk request section shows:
      Request type: No match
      Channel: JIRA

      There is a pull-down menu which can be used to set the Request Type here. In our configuration there is only ever 1 type of Request Type which is applicable to any particular issue type. If this is the case, why not set it automatically.

      Alternatively, expose the option to set the Request Type on the creation screen.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              478c5b28ee5c Joe Smith
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync