Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3425

Add a drop down option "Service Desk Request" to the Create issue button in JIRA.

XMLWordPrintable

    • 1
    • 15
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Problem Definition

      Currently an agent can create a JIRA Service Desk issue within JIRA without a request type specified. You can specify the request type on the view issue screen but not the create issue screen. You can specify the issue type but it will not fill out the request type according to issue type>request match. It will produce a "No Match" on the view issue screen after the issue is created even though the issue type is configured for the request type. This is because one issue type can map to several request types so this can't be done automatically.

      See Configuring request types and workflows and How JIRA and JIRA Service Desk work together for reference.

      Since you cannot specify the request type from create issue view within JIRA. It leaves a possibility that a customer may not be updated if an agent creates an issue from within JIRA.

      Suggested Solution

      Since issues should be created via the customer issues should be created via the customer portal by design. Agents should be directed to a JIRA Service Desk Create issue screen where the request type can be specified via either the customer portal, a modified create issue screen, or request type appears on the create issue screen if project type = Service Desk is specified.

              a620038e6229 Jehan Gonsalkorale
              jcastro Jose Castro (Inactive)
              Votes:
              34 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: