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

Customer Request Type not Set when issue created from inside JIRA

XMLWordPrintable

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

      Issue Summary

      When a Service Desk issue is created directly in JIRA, the Customer Request Type is not set in the created issue.

      Steps to reproduce.
      • Create a Service Desk project.
      • Create an issue in this project directly from JIRA.
      • Open the issue and look at the "Service Desk Request > Request Type" section.
      • This will always show "No Match"
      Expected Result/Behaviour
      • Service Desk picks the default Customer Request Type.
      Actual Behaviour
      • Service Desk shows No match in the field in red.
      Possible Fixes:
      • Service Desk sets a default value for the field.
      • This field is automatically added to a Service Desk issue creation screen and is set to required.

        1. SD Customer Request Type.PNG
          SD Customer Request Type.PNG
          53 kB
        2. SetRequestType.png
          53 kB

            [JSDSERVER-2006] Customer Request Type not Set when issue created from inside JIRA

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304045 ] New: JAC Bug Workflow v3 [ 3125497 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058003 ] New: JSD Bug Workflow v5 - TEMP [ 2304045 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2055509 ] New: JSD Bug Workflow v5 [ 2058003 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956201 ] New: JSD Bug Workflow v5 - TEMP [ 2055509 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615011 ] New: JSD Bug Workflow v5 [ 1956201 ]
            jonah (Inactive) made changes -
            Description Original: h5. Issue Summary
            When a Service Desk issue is created directly in JIRA, the Customer Request Type is not set in the created issue.

            h5. Steps to reproduce.
            - Create a Service Desk project.
            - Create an issue in this project directly from JIRA.
            - Open the issue and look at the "_Service Desk Request > Request Type_" section.
            - This will always show "*No Match*"
            !SD Customer Request Type.PNG|thumbnail!

            h5. Expected Result/Behaviour
            - Service Desk picks the default Customer Request Type.

            h5. Actual Behaviour
            - Service Desk shows No match in the field in red.

            h5. Possible Fixes:
            - Service Desk sets a default value for the field.
            - This field is automatically added to a Service Desk issue creation screen and is set to required.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-2006].
              {panel}

            h5. Issue Summary
            When a Service Desk issue is created directly in JIRA, the Customer Request Type is not set in the created issue.

            h5. Steps to reproduce.
            - Create a Service Desk project.
            - Create an issue in this project directly from JIRA.
            - Open the issue and look at the "_Service Desk Request > Request Type_" section.
            - This will always show "*No Match*"
            !SD Customer Request Type.PNG|thumbnail!

            h5. Expected Result/Behaviour
            - Service Desk picks the default Customer Request Type.

            h5. Actual Behaviour
            - Service Desk shows No match in the field in red.

            h5. Possible Fixes:
            - Service Desk sets a default value for the field.
            - This field is automatically added to a Service Desk issue creation screen and is set to required.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-2006 [ JSDCLOUD-2006 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server New: affects-cloud affects-server
            Steve Bastick made changes -
            Attachment New: SetRequestType.png [ 223811 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: