Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
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:
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.
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.
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.
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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