-
Suggestion
-
Resolution: Unresolved
-
None
-
25
-
47
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
Hi All,
You can now import SLA’s from your existing projects to new ones! This has been available since Jira Service Desk 3.8.x.
To find out more check out the release notes: https://confluence.atlassian.com/servicedesk/jira-service-desk-3-8-x-release-notes-936509559.html
On behalf of the JSD team I want to thank all of you for your patience.
— JIRA Service Desk Team
In our setup, we have a servicedesk project per customer. Most of the SVD setup (like workflow, calendars & standard offered SLA metrics) are the same for all projects, while other aspects (users/project roles/...) are specific for each SVD project.
having tens of SVD projects, means each time the same SLAsetup needs to be configured manually:
- SLA metrics
- Calendars
- ...
.. while other specifically generated setup is not wanted:
- workflow
- screens
- issuetypes
- ...
Being able to control which defaults are used during 'create project' wizard, would be really helpful.
Alternatively, a clone/copy-from-existing SVD project would work as workaround -> if this were possible, we could use a template project to copy from.
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
-
- Future Consideration
- was cloned as
-
- Closed
-
- Gathering Interest
- links to
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-191] Service Desk templates
Hey guys,
This seems to be a not hard feature to be implemented and I am sure that it would bring a lot of value for larger organizations that need to make sure that projects are being created with a specific standard.
Any updates?
Hello Mohamed,
from a Solution Partner perspective, we largely benefit from the fact that multiple Apps are now able to copy/clone Service Desk projects, such as ScriptRunner, Project Configurator and Configuration Manager.
As - at least the latter 2 - generate Snapshots in a human-readable format such as XML or JSON, it's also very easy to duplicate those snapshot-files and modify them to your needs (e.g. when you want to change individual things in the project before importing it again).
That way we have both cloned individual JSD projects and created a multitude of slightly differentiating projects for large scale customers that need a Service Desk project for each of their clients.
Considering that you can use either of those apps for different other cases (such as building projects on Staging and easily migrate them to Prod), they might be worth the money for you - even though at first you just bought them for simply copying JSD projects.
I hope that helps!
Regards,
Philipp
I'm so curious about how other JSD users are managing multiple SD projects... Do they manually create a project each time? Can you imagine a mistake made at customer permissions level? Direct negative business impact...
It's a bit sad to see that after 6 years, this feature is still at 'Gathering Interests' stage...
Crazy that this isn't already a feature. I have so many service desks to create that take almost half an hour each time.
Hi! To save your time, the ability to copy / clone JSD projects from one Jira to another is possible with Project Configurator for Jira
PC4J helps you with the consistency problems and allows better organisation.
An essential feature to keep consistence across projects for different organisations. Please provide an update on when this will be incorporated and where it is on the roadmap.
+1 We definitely would benefit from this feature and can't believe it doesn't exist already.