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
          image-2015-11-17-17-46-42-821.png
          112 kB
        2. screenshot-1.png
          screenshot-1.png
          74 kB
        3. screenshot-2.png
          screenshot-2.png
          49 kB
        4. screenshot-3.png
          screenshot-3.png
          100 kB
        5. screenshot-4.png
          screenshot-4.png
          66 kB

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

            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

            Hi

            I have linked some other open issues to this ticket that I would recommend voting for, and watching for updates.

            The issue here is that the Customer Request Type field can not be added to the Field Screens. As well as this, we can not currently automatically assign a request type using an Automation rule. But if either of those would be useful for you, I recommend commenting on appropriate issue.

            Finally, when a ticket is created through JIRA and has no Request Type associated, the reporter and Request Participants will miss out on Service Desk specific emails. We have another open issue that has a potential solution to address this as well.

            While I can not provide an ETAs for any of the mentioned issues, the best I can say is to watch those tickets for updates.

            Regards
            Matt
            JIRA Service Desk developer

            Matthew McMahon (Inactive) added a comment - Hi I have linked some other open issues to this ticket that I would recommend voting for, and watching for updates. The issue here is that the Customer Request Type field can not be added to the Field Screens. As well as this, we can not currently automatically assign a request type using an Automation rule. But if either of those would be useful for you, I recommend commenting on appropriate issue. Finally, when a ticket is created through JIRA and has no Request Type associated, the reporter and Request Participants will miss out on Service Desk specific emails. We have another open issue that has a potential solution to address this as well. While I can not provide an ETAs for any of the mentioned issues, the best I can say is to watch those tickets for updates. Regards Matt JIRA Service Desk developer

            Another note on this, I cant search this field either, which means it's not easy to find which have been missed?

            Donna Menhennett added a comment - Another note on this, I cant search this field either, which means it's not easy to find which have been missed?

            Further to this, which I believe is related, even though I have the "Request Participants" field enabled on my "Create Issue" screen, it doesn't show up?

            The "Edit Screen" displays the field once the Service Desk Request Type is set.

            Are these related, and if yes, hopefully the answer you provide for the first question will fix this up!

            Thanks in advance!

            Some helpful screenshots



            Donna Menhennett added a comment - Further to this, which I believe is related, even though I have the "Request Participants" field enabled on my "Create Issue" screen, it doesn't show up? The "Edit Screen" displays the field once the Service Desk Request Type is set. Are these related, and if yes, hopefully the answer you provide for the first question will fix this up! Thanks in advance! Some helpful screenshots

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

                Created:
                Updated:
                Resolved: