• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Global Configuration
    • 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 am finding it takes about 2 hrs to create a new service desk. We will eventually need to create about 50+ for the major customers of our SAAS product. The management time for this is outweighing the benefits of using.

      We require : 'Create Service Desk for "Customer B", user "CustB User", project "CustB project", using Template "Customer A Service Desk" '.

      i.e. Service desk desperately needs templates for:
      issue types on the customer portal
      sla definitions
      calendar
      single project permissions (i.e. copy from existing permission scheme, create new and add user group)
      etc.

      If we want to adjust the SLAs for all service desks, we should be able to change a reference SLA scheme, not edit each desk.

      Alternatively:
      Allow a single service desk to be setup with everything parameterised from the service desk name down to permissions etc. Requirement is for user from customer A to only see the single customer A project issues, SLAs etc.

          Form Name

            [JSDSERVER-294] Service desk templates for create and manage.

            Raman Auseikou made changes -
            Link New: This issue duplicates JSDSERVER-13623 [ JSDSERVER-13623 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011496 ] New: JAC Suggestion Workflow 3 [ 3651022 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Eduardo Santos made changes -
            Link New: This issue duplicates JSDSERVER-6495 [ JSDSERVER-6495 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2664392 ] New: JAC Suggestion Workflow [ 3011496 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324752 ] New: Confluence Workflow - Public Facing v4 [ 2664392 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2054153 ] New: JSD Suggestion Workflow - TEMP [ 2324752 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049497 ] New: JSD Suggestion Workflow [ 2054153 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1279481 ] New: JSD Suggestion Workflow - TEMP [ 2049497 ]
            jonah (Inactive) made changes -
            Description Original: I am finding it takes about 2 hrs to create a new service desk. We will eventually need to create about 50+ for the major customers of our SAAS product. The management time for this is outweighing the benefits of using.

            We require : 'Create Service Desk for "Customer B", user "CustB User", project "CustB project", using Template "Customer A Service Desk" '.

            i.e. Service desk desperately needs templates for:
            issue types on the customer portal
            sla definitions
            calendar
            single project permissions (i.e. copy from existing permission scheme, create new and add user group)
            etc.

            If we want to adjust the SLAs for all service desks, we should be able to change a reference SLA scheme, not edit each desk.

            Alternatively:
            Allow a single service desk to be setup with everything parameterised from the service desk name down to permissions etc. Requirement is for user from customer A to only see the single customer A project issues, SLAs etc.
            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-294].
              {panel}

            I am finding it takes about 2 hrs to create a new service desk. We will eventually need to create about 50+ for the major customers of our SAAS product. The management time for this is outweighing the benefits of using.

            We require : 'Create Service Desk for "Customer B", user "CustB User", project "CustB project", using Template "Customer A Service Desk" '.

            i.e. Service desk desperately needs templates for:
            issue types on the customer portal
            sla definitions
            calendar
            single project permissions (i.e. copy from existing permission scheme, create new and add user group)
            etc.

            If we want to adjust the SLAs for all service desks, we should be able to change a reference SLA scheme, not edit each desk.

            Alternatively:
            Allow a single service desk to be setup with everything parameterised from the service desk name down to permissions etc. Requirement is for user from customer A to only see the single customer A project issues, SLAs etc.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-294 [ JSDCLOUD-294 ]

              Unassigned Unassigned
              ccf5e98c34fc Phil Waight
              Votes:
              27 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: