-
Suggestion
-
Resolution: Duplicate
-
None
-
None
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.
- duplicates
-
JSDCLOUD-8326 Service Desk templates
- Closed
-
JSDSERVER-191 Service Desk templates
- Gathering Interest
-
JSDSERVER-13623 Service Desk templates
- Gathering Interest
- relates to
-
JSDCLOUD-294 Service desk templates for create and manage.
- Closed
-
JSDSERVER-2106 As a Service Desk Administrator, I would like to be able to copy Automation Rules in my project
- Closed
Form Name |
---|
[JSDSERVER-294] Service desk templates for create and manage.
Link | New: This issue duplicates JSDSERVER-13623 [ JSDSERVER-13623 ] |
Workflow | Original: JAC Suggestion Workflow [ 3011496 ] | New: JAC Suggestion Workflow 3 [ 3651022 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue duplicates |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664392 ] | New: JAC Suggestion Workflow [ 3011496 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324752 ] | New: Confluence Workflow - Public Facing v4 [ 2664392 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JSD Suggestion Workflow [ 2054153 ] | New: JSD Suggestion Workflow - TEMP [ 2324752 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2049497 ] | New: JSD Suggestion Workflow [ 2054153 ] |
Workflow | Original: JSD Suggestion Workflow [ 1279481 ] | New: JSD Suggestion Workflow - TEMP [ 2049497 ] |
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. |
Link |
New:
This issue relates to |