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

As an agent I would like to raise a request through the Customer Portal on behalf of a customer

XMLWordPrintable

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

      If an agent creates an issue on behalf of a user through the customer portal, they can't specify the reporter. This means they need to create the issue, then edit it to specify that reporter.

      If they use the normal create issue screen all the pre-populated fields in the Customer Portal form will not be used. It adds a friction point for the agent as it increases effort.

          Form Name

            [JSDSERVER-51] As an agent I would like to raise a request through the Customer Portal on behalf of a customer

            Judd (Inactive) added a comment -

            aaron3 there is an open issue for the ability to edit the Customer Request Type field: JSD-42. I'd encourage you to vote on this and add any comments about your use case.

            Cheers,
            Judd
            ---------------
            Designer, JIRA Service Desk

            Judd (Inactive) added a comment - aaron3 there is an open issue for the ability to edit the Customer Request Type field: JSD-42 . I'd encourage you to vote on this and add any comments about your use case. Cheers, Judd --------------- Designer, JIRA Service Desk

            Aaron Shipman added a comment -

            Why cant the Customer Request Type Field be available for editing. So Historic issues can be migrated to a customer portal

            OR new issues created by Devs can be pushed out to the portal.

            why cant users just set the correct field value on edit?

            Aaron Shipman added a comment - Why cant the Customer Request Type Field be available for editing. So Historic issues can be migrated to a customer portal OR new issues created by Devs can be pushed out to the portal. why cant users just set the correct field value on edit?

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Votes:
              25 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: