• 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.

      example use cases
      • Associate existing tickets and tickets that come through email or various other sources with a Service Desk (when the Customer Request Type field isn't filled in, tickets won't be displayed in the Customer Portal).
      • Move tickets between Service Desks (triage).
      • Create and move tickets on customers' behalf, e.g. after a phone call.

        1. screenshot-1.png
          screenshot-1.png
          26 kB
        2. screenshot-2.png
          screenshot-2.png
          50 kB

            [JSDSERVER-42] Allow "Customer Request Type" to be manually edited

            We're showing this isn't resolved either. The reporter assigned by the service desk agent still cannot see the issues via the portal or the link from the email.

            Kristin Bitler (mty.k12) added a comment - We're showing this isn't resolved either. The reporter assigned by the service desk agent still cannot see the issues via the portal or the link from the email.

            I agree, this matter isn't resolved and it would save a lot of duplicated effort.

            Justin Lynch added a comment - I agree, this matter isn't resolved and it would save a lot of duplicated effort.

            Yes, this issue has not been fixed as of July 2017. How can I manually edit Customer Request Types on tickets? Moving is not an option as several Request Types share the same Issue Type.

            Adriana Wolfe added a comment - Yes, this issue has not been fixed as of July 2017. How can I manually edit Customer Request Types on tickets? Moving is not an option as several Request Types share the same Issue Type.

            What was the resolution to mark this done?

            Barry Kaplan added a comment - What was the resolution to mark this done?

            Why is this set as closed ?

            Daniel Hrvatin added a comment - Why is this set as closed ?

            RL Prasad added a comment -

            And honestly, i don't see the advantage of having the request type in the view screen, infact the request type group would be beneficial to be displayed for future reports. If i want to get reports for Access request, i need to select several request types rather than selecting one group called - Access request.

            RL Prasad added a comment - And honestly, i don't see the advantage of having the request type in the view screen, infact the request type group would be beneficial to be displayed for future reports. If i want to get reports for Access request, i need to select several request types rather than selecting one group called - Access request.

            RL Prasad added a comment -

            And most importantly, i don't see any difference between request type and issue type from an agen\support perspective. Request Type is for customer, Issue type is for agent. And in real world , a request can be several issue types. For example: Request Type- Access Request, issue type can be an issue(unable to login, permission issues), or New user(which has different workflow and include approvals),

            RL Prasad added a comment - And most importantly, i don't see any difference between request type and issue type from an agen\support perspective. Request Type is for customer, Issue type is for agent. And in real world , a request can be several issue types. For example: Request Type- Access Request, issue type can be an issue(unable to login, permission issues), or New user(which has different workflow and include approvals),

            What doesnt make sense though is that I cant map one request type to several issue types, which means if I want to keep my service portal "clean" with only one option for customers (simple internal support) but I would like several issue types for our own sake internally, thats not an option.

            Stian Bentsen Sveen added a comment - What doesnt make sense though is that I cant map one request type to several issue types, which means if I want to keep my service portal "clean" with only one option for customers (simple internal support) but I would like several issue types for our own sake internally, thats not an option.

            You can only switch to a request type, which is mapped to your issue type. If the current issue hasn't a mapping, you can't select a request type - which make sense.

            bitvoodoo ag added a comment - You can only switch to a request type, which is mapped to your issue type. If the current issue hasn't a mapping, you can't select a request type - which make sense.

            Seems I have the similar issue. The screen allows you to change the Request Type but all the options are grayed out.

            Joe Beitler added a comment - Seems I have the similar issue. The screen allows you to change the Request Type but all the options are grayed out.

              Unassigned Unassigned
              imaduro Ivan Maduro (Inactive)
              Votes:
              82 Vote for this issue
              Watchers:
              75 Start watching this issue

                Created:
                Updated:
                Resolved: