Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-4801

Unable to copy SLA for service desk using Copy project

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Done
    • Low
    • Resolution: Done
    • 6.15.0
    • 6.16.0
    • Built-in Scripts
    • None
    • SR4J Sprint 89
    • 2.7

    Description

      Steps to replicate :

      1. Create a new service desk project
      2. Go to the built-in Scripts section in the ScriptRunner menu
      3. Search for Copy project
      4. Click on Copy project
      5. Use the following Copy project configuration :

        Ensure that copy SLA is checked
      6. You will see the following error as per the screenshot attached :

      Current behavior: it does not copy the SLA over successfully and ends with the following error

      Error: No signature of method: static com.onresolve.scriptrunner.canned.jira.utils.servicedesk.ServiceDeskUtils.copySDSLA() is applicable for argument types: (com.atlassian.jira.user.DelegatingApplicationUser, com.atlassian.jira.project.ProjectImpl...) values: [admin(JIRAUSER10000), Project: CS, Project: CS4]
      groovy.lang.MissingMethodException: No signature of method: static com.onresolve.scriptrunner.canned.jira.utils.servicedesk.ServiceDeskUtils.copySDSLA() is applicable for argument types: (com.atlassian.jira.user.DelegatingApplicationUser, com.atlassian.jira.project.ProjectImpl...) values: [admin(JIRAUSER10000), Project: CS, Project: CS4]
      	at com.onresolve.scriptrunner.canned.jira.admin.CopyProject.copyServiceDeskModules(CopyProject.groovy:681)
      	at com.onresolve.scriptrunner.canned.jira.admin.CopyProject.doCopyProject(CopyProject.groovy:647)
      	at com.onresolve.scriptrunner.canned.jira.admin.CopyProject$doCopyProject.callCurrent(Unknown Source)
      	at com.onresolve.scriptrunner.canned.jira.admin.CopyProject.execute(CopyProject.groovy:363)
      	at com.onresolve.scriptrunner.canned.jira.admin.CopyProject.execute(CopyProject.groovy)

      Expected behavior: the project should be copied over with the SLA successfully

      Workaround : Import the SLA separately after copying the project without the CopySLA option. This can be done via Jira native SLA. import feature as documented in the link Importing SLA

      Attachments

        Activity

          People

            twozniak Tomasz Wozniak [X] (Inactive)
            dlooi Der Lun Ooi [X] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: