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

Service Desk: Built-in Script "Copy Project" creates invalid queue JQL search

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Done
    • Low
    • Resolution: Done
    • 6.5.0-p5, 6.7.0
    • 6.18.0
    • Built-in Scripts
    • SR4J Sprint 90
    • 1.7

    Description

      Description
      When a Jira Service Desk Admin copies a project using the built-in script "Copy project", the new project's "Issues to show" search criteria is prefixed with a project code that doesn't match the new project.

      Steps to reproduce

      1. In Jira Service Desk project admin > Manage Apps
      2. Navigate to ScriptRunner's Built-in scripts
      3. Select "Copy project"
      4. Select a parent Service Desk project
      5. Select 'Copy queue' as an option
      6. Click Run
      7. Once complete, navigate to the new Project created.
      8. Navigate to the new project's queue
      9. Click More Options (...) > Edit Queue
      10. Review the 'Issues to show' input field

      Expected behaviour
      The "Issues to show" field is prefixed with the new project key, or nothing at all. This allows new tickets created via the project's service desk to appear in the queue automatically.

      Actual behaviour
      The "Issues to show" field is prefixed with a parent project key that doesn't match the new project key. This means new tickets created through the service desk don't appear in the queue unless you use the workaround below.

      Workaround
      Remove the prefix "{{project = KEY AND }}" from the "Issues to show" field.

      Attachments

        Issue Links

          Activity

            People

              twozniak Tomasz Wozniak [X] (Inactive)
              jbaldwin Joe Baldwin
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: