new set of schemes per projet - How this can be used?

Dayana Delgado

This question is in reference to Atlassian Documentation: Defining a project

We are wondering, how can this feature of creating new  set of schemes per new projet can be used? How can you keep a certain uniformity? we understand there is the option of creating projets from existing ones, but we are trying to take advantage of all fonctions in JIRA. 

When you create a new project from a template, that project is created with its own fresh set of schemes. These schemes are:

• a permission scheme
• a notification scheme
• an issue security scheme
• a workflow scheme
• an issue type scheme
• an issue type screen scheme
• a field configuration scheme

Myra_Rebillard

Hi Dayana,

I'll address your question regarding uniformity.  This is a lesson learned for us.

We make use of the schemes by defining a template projects.  Our template projects define all the above - issue type schemes, permission schemes, etc.

Now, all projects of type A, when they are created, their project configurations are modified so that they reference the schemes from the template project.  So all projects of type A will have the same issue types, screens, fields, etc. Same goes with all projects of type B which is configured by another template project.

So if you want to change anything, you need only change the template project, and all projects referencing that configuration will automatically get those changes.  Of course this has its pros and cons, but if you're concerned about uniformity, I think this is the way to go, otherwise you could have duplicate configuration items (schemes) that have the same definitions, or same project types all modified a little differently that could make it difficult to administer, monitor, and potentially use (if people switch from project to project).

Best,

Myra