nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to reduce repetitive setup for new projects in GreenHopper / JIRA.

Prem Mariappan

Hi,

We do many small projects. I'm trying to reduce the overhead in the setup of each new project in JIRA / GreenHopper.

At present, I do a bulk import of standard issues, and that saves a tremendous amount of time.

But how do I go about doing the following automatically with each new project?

add the same set of 'Components' to each project?
automatically use the Scrum 'Project Template'
automatically use GreenHopper Scrum 'Issue Type Scheme'

Is there a way of defining a default project configuration template of some sort? Since we're doing many small projects typically 1-4 weeks, it would save us a lot of time.

Thank you.

Prem.

Comments

Christian Czaia [Decadis AG]

Hey,

basically what you're trying to do is clone a project or use a template which is not possible in a standard JIRA configuration.

You might want to check this post:

https://answers.atlassian.com/questions/10982/can-i-copy-a-project-to-use-as-a-starting-point-for-creating-a-new-custom-project

and the plugins mentioned in here:

Jamie's Script Runner:

https://plugins.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner

and

https://studio.plugins.atlassian.com/wiki/display/JCLI/JIRA+Command+Line+Interface

Cheers Christian

Renjith Pillai

Jamie's script runner can do copy projects.

https://studio.plugins.atlassian.com/wiki/display/GRV/Script+Runner

cedricboivin@nm

There is my technique.

You create your template project In Jira. You give to the project a key, someting like TPROJECT. You backup your jira in an XML file, in the jira administration panel.

After that, you take the backup (xml file) and put it in the import folder. Now you create your new project (empty) in Jira.

Suppose your key is NEWPROJECT. Go in your XML file, and make an FIND and Replace of your TPROJECT key and replace it to your new key NEWPROJECT.

After that go in imporation project in your jira administration. Import your xml file, and chose your template project in the list. Uncheck the checkbox to replace the project info.

And there you got your importation tools ;-)

have fun !!!

Prem Mariappan

Hi Cédric - what a fantastic solution! Thank you. Great suggestion.

Mattias Hallqvist

Am I correct in that this method only imports issues, and not project settings (schemes, components, mappings etc)?

TJ Baker

Thanks for sharing this workaround ... for the time being it's better than having to re-create everytying with every project that we repeat items with!

TJ Baker

Script runner is only good if you're not OnDemand.

The XML / bakcup approach is great if you are, as a workaround.

Really, though, 'Copy Project' (or Project Templates) is a base function that is provided in most 'hosted' PM systems these days, and should be with Jira as well, imo.

Ravi Sagar _Sparxsys_

There is an add-on for cloning a project: https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-clone-project-plugin

It is not supported now but I use it regularly, it works perfectly.

JFT

Hi Prem,

The Gaia plugin will help you do exactly that (see http://bit.ly/RwwjGQ)

Basically, you can create project templates that will include:

- The full scheme configuration that you will be using in your project

- The type of JIRA Agile project (Scrum, Kanban)

- List of predefined components and versions

- Pre-defined dashboards

- A list of pre-defined tasks

It can even automatically create a Confluence Space (based on a template) that you might want to associate to your JIRA project for documentation.

These project templates can be selected when creating new projects in JIRA.

Cheers,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

template

scrum

configuration