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

Dynamically setting "Service Desk Request Type" when creating an issue in Jira

    • Icon: Suggestion 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.

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

      Hey guys!

      Instead of creating a ticket in the service desk portal, we often create tickets from the "Create" button (project button) in JIRA.

      The problem when we do this is that the Service Desk Request Type shows up as "No Match" even though I have setup the request type in the service desk.

      Example:
      https://visualjazz.jira.com/projects/SJSD/queues/353/SJSD-14

      Is there any way to set this so that this happens automatically?

      Otherwise if we request participants before doing this, they do not receive the notification.

      Thanks!

        1. image-2015-11-17-17-46-42-821.png
          112 kB
          Donna Menhennett
        2. screenshot-1.png
          74 kB
          Donna Menhennett
        3. screenshot-2.png
          49 kB
          Donna Menhennett
        4. screenshot-3.png
          100 kB
          Donna Menhennett
        5. screenshot-4.png
          66 kB
          Donna Menhennett

          Form Name

            [JSDSERVER-2962] Dynamically setting "Service Desk Request Type" when creating an issue in Jira

            Divyanshi made changes -
            Remote Link Original: This issue links to "JSDS-564 (JIRA Server (Bulldog))" [ 285670 ] New: This issue links to "JSMDC-564 (JIRA Server (Bulldog))" [ 285670 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011994 ] New: JAC Suggestion Workflow 3 [ 3649545 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665649 ] New: JAC Suggestion Workflow [ 3011994 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2326078 ] New: Confluence Workflow - Public Facing v4 [ 2665649 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

            Hi,

            I can confirm this is still a problem in JIRA server 7.5.0 and JSD 3.8.1. We recently added a feature to clone issue from one JSD project to another and we add agents from one project as request participants in the process, so they can be notified of updates on the issue as it progresses. This feature was added to aid in cross-dept hand-off of work and the lack of notifications is a problem.

            Any ETA on a fix, or perhaps there is a workaround available?

            Thanks,
            Kevin Beattie

            Kevin Beattie added a comment - Hi, I can confirm this is still a problem in JIRA server 7.5.0 and JSD 3.8.1. We recently added a feature to clone issue from one JSD project to another and we add agents from one project as request participants in the process, so they can be notified of updates on the issue as it progresses. This feature was added to aid in cross-dept hand-off of work and the lack of notifications is a problem. Any ETA on a fix, or perhaps there is a workaround available? Thanks, Kevin Beattie
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2054083 ] New: JSD Suggestion Workflow - TEMP [ 2326078 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049412 ] New: JSD Suggestion Workflow [ 2054083 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280705 ] New: JSD Suggestion Workflow - TEMP [ 2049412 ]
            Matthew McMahon (Inactive) made changes -
            Remote Link New: This issue links to "JSDS-564 (JIRA Server (Bulldog))" [ 285670 ]
            jonah (Inactive) made changes -
            Description Original: Hey guys!

            Instead of creating a ticket in the service desk portal, we often create tickets from the "Create" button (project button) in JIRA.

            The problem when we do this is that the Service Desk Request Type shows up as "No Match" even though I have setup the request type in the service desk.

            Example:
            https://visualjazz.jira.com/projects/SJSD/queues/353/SJSD-14
             !image-2015-11-17-17-46-42-821.png|thumbnail!

            Is there any way to set this so that this happens automatically?

            Otherwise if we request participants before doing this, they do not receive the notification.

            Thanks!
            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-2962].
              {panel}

            Hey guys!

            Instead of creating a ticket in the service desk portal, we often create tickets from the "Create" button (project button) in JIRA.

            The problem when we do this is that the Service Desk Request Type shows up as "No Match" even though I have setup the request type in the service desk.

            Example:
            https://visualjazz.jira.com/projects/SJSD/queues/353/SJSD-14
             !image-2015-11-17-17-46-42-821.png|thumbnail!

            Is there any way to set this so that this happens automatically?

            Otherwise if we request participants before doing this, they do not receive the notification.

            Thanks!

              Unassigned Unassigned
              c71dcdfb31c3 Donna Menhennett
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: