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

Single Customer Portal, multiple Service Desk back ends

XMLWordPrintable

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

      I would be great if Service Desk worked a little bit more like JIRA Agile Boards, allowing to mix-and-match multiple projects in the back end, but a single customer portal entry point.

      We have a scenario where we want IT, Software, and other groups to have their own Service Desk back end, queues and projects, but would still like to offer a single customer portal front end to our users.

      This would reduce the confusion on our users ( who can pick all their issue types from a single interface). As well as our agents, with each department working in their own backend with potentially separate SLA, queues, and other settings.

          Form Name

            [JSDSERVER-283] Single Customer Portal, multiple Service Desk back ends

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011831 ] New: JAC Suggestion Workflow 3 [ 3649336 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665272 ] New: JAC Suggestion Workflow [ 3011831 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324750 ] New: Confluence Workflow - Public Facing v4 [ 2665272 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2054151 ] New: JSD Suggestion Workflow - TEMP [ 2324750 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049495 ] New: JSD Suggestion Workflow [ 2054151 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280581 ] New: JSD Suggestion Workflow - TEMP [ 2049495 ]
            jonah (Inactive) made changes -
            Description Original: I would be great if Service Desk worked a little bit more like JIRA Agile Boards, allowing to mix-and-match multiple projects in the back end, but a single customer portal entry point.

            We have a scenario where we want IT, Software, and other groups to have their own Service Desk back end, queues and projects, but would still like to offer a single customer portal front end to our users.

            This would reduce the confusion on our users ( who can pick all their issue types from a single interface). As well as our agents, with each department working in their own backend with potentially separate SLA, queues, and other settings.             		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-283].
              {panel}

            I would be great if Service Desk worked a little bit more like JIRA Agile Boards, allowing to mix-and-match multiple projects in the back end, but a single customer portal entry point.

            We have a scenario where we want IT, Software, and other groups to have their own Service Desk back end, queues and projects, but would still like to offer a single customer portal front end to our users.

            This would reduce the confusion on our users ( who can pick all their issue types from a single interface). As well as our agents, with each department working in their own backend with potentially separate SLA, queues, and other settings.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-283 [ JSDCLOUD-283 ]
            Owen made changes -
            Workflow Original: TTT: Simple Issue Tracking Workflow [ 620945 ] New: JSD Suggestion Workflow [ 1280581 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            annasris (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 85661 ] New: This issue links to "Page (Extranet)" [ 85661 ]

              Unassigned Unassigned
              e887a69c641b Olivier Ozoux
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: