XMLWordPrintable

    • 23
    • 39
    • 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 Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Atlassian status update as of 29th November 2018

      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.

              Unassigned Unassigned
              ben.de.pauw1 BenP
              Votes:
              507 Vote for this issue
              Watchers:
              287 Start watching this issue

                Created:
                Updated: