Create new project using existing workflows

I'm new to administering JIRA but I've come across a frustrating point: every new JIRA project seems to create a new Workflow and Workflow Scheme (at least) with the project name. Since I want to set these new projects to use an existing common Workflow (Scheme), it's annoying to have to go through this process with each new project:

  1. Change the project's workflow and scheme to point to the common one
  2. Switch to the list of workflow schemes
  3. Click "inactive" to show the now inactive scheme
  4. Delete the workflow scheme
  5. Switch to the list of workflows
  6. Click "inactive" to show the now inactive workflow
  7. Delete the workflow

I'm probably missing a few steps because I don't remember the specifics, but it's a needlessly complex process.

Is it possible to create a new project without all the extra stuff getting created that I will end up deleting anyway?

Thanks in advance.

 

5 answers

1 accepted

Hey Ethan,

JIRA Automatically creates a new scheme

This occurs if you create a project using one of the JIRA Project Templates. For example, JIRA Agile Project. To avoid automatically creating these schemes each time a project is created, select the JIRA Classic Project type during creation. This will assign all the existing default schemes to the project. 

Once you create the project, you will have to manually change each scheme to use your existing scheme.

Workaround

You can build your own project template and use it to create projects to use a specific scheme when created. Take a look at https://developer.atlassian.com/display/JIRADEV/Creating+a+Project+Template

There is no classic project type (7.1.7). We do not want to create all the not needed stuff (schemes, workflows...) by creating a new project. (It is much work to delete all this stuff after creating the new project with the wanted schemes, workflows....)

So please tell us an option to create projects without this.

Did you manage to find a resolution to this issue? Or do we have to accept the fact that every time a project is created a workflow is created too? 

I think in JIRA Software (7.02) there is no "classic project type" anymore. 

Upgraded to 7.1.2...where is CLASSIC ????

In JIRA 6.4.13 there is no "Classic project type", but there's an option called "JIRA Default Schemes" which seems to be equivalent. I've just created a project with it, and for all the Issue Types the workflow is "jira", the field configuration is "Default Field Configuration" and the screen scheme is almost always the "Default Screen Scheme". I haven't understood the logic by which other screen schemes have been chosen for some Issue Types, but it doesn't matter. What matters is that it hasn't created anything, so I don't have to delete anything.

Sure, I still have to reassign all the Issue Types to the correct schemes. Frankly I'd prefer to be able to create a project this is completely empty, but it looks like there's no way to do it.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,760 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot