Is there a way to transfer all project settings/schemes etc onto another project?

[lukasz spychalski]

I need to set up about 30 projects in JIRA Service Desk - is there any way to set up a template or transfer all project settings / screens / issue types / workflows / schemes etc onto a new project?

[Boris Georgiev [Appfire]]

You can use Configuration Manager for JIRA to create a "snapshot" of the configuration of a single project which then you can use as a template for creating new projects.

This can be achieved in a few simple steps:

1. Create a Project snapshot of the "template" project
2. Deploy this snapshot using the "New Project" deploy mode

This will effectively create a new project and assign it all the schemes that the "template" project is using. 

Note that neither Script Runner nor Configuration Manager still support Service Desk so you'll have to manually copy the service desk settings.

[Michael Partyka]

Hi Lukasz,

You should install ScriptRunner plugin and used build in script Copy Project

Copy Project

This script allows you to create a new project based on another.
It will copy:

• Schemes
• Role memberships
• Custom field configurations
• Optionally, versions and component
• Optionally, all issues and their attachments in the source project.
  • This is useful for creating template projects with issues with template documents.
• Certain Greenhopper constructs, such as version hierarchies, board templates etc
• Filters and dashboards that begin with the project key
  • This is useful when your provisioning process requires giving new users a tailored dashboard and a set of filters related to their project (this is a niche requirement that you're unlikely to need or want)

From version 2.1: If you choose to copy issues, all links on issues in the source project will be copied, with one exception. Intra-project links on the project will be reproduced on the respective issues in the copied project. For instance, if you are copying project A to project B, and in A issue A-1 depends on A2, then B-1 will depend on B2. Again, useful for seeding a project with sample issues for onboarding new teams.