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

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

2 answers

1 accepted

0 votes
Accepted answer

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).



Thanks Mira, this will help for sure. Template project you mean using the fonction "Create sample data" ? or where can I configure those project templates? 


Hi Dayana,

A template project for us is just a regular project.  It basically has no data, but it has schemes.

Project Template A

Issue Types: Project Template A Issue Type Scheme

Workflows: Project Template A Issue Type Workflow Scheme

Screens: Project Template A Issue Type Screen Scheme


So now when you have an actual project that you want data in it, you would do this:

Delgado Project

Issue Types:Project Template A Issue Type Scheme

Workflows: Project Template A Isuse Type Workflow Scheme

Screens: Project Template A Issue Type Screen Scheme


Hope that's clearer.  I hope you get some other comments.  It would be good to hear how others have accomplished this in their organizations as well!



Got you! thats what I was planning on doing.. I though there was another better way without having to change the whole schemes every time. 

Thanks a lot!

Hello Dayana Delgado

English it's not my native language - I'm from Brazil - but lemme try help you. 

  1. how can this feature of creating new  set of schemes per new project can be used?
    1. you can setup access, notifications, workflows and everything else with your necessity.

  2. How can you keep a certain uniformity?
    1. you could create group of projects based on schemes, and you can see at scheme what projects are using it.

And I think you want to know how use the schemes at projects right? So...

The schemes at JIRA is a powerful tool to setup your project.

  1. Permission scheme: You can setup permission based on group, so you can put some limits to access a project.
    1. Here you can see how creating a permission scheme
    2. Here you can see how maning project permission
  2. Notification scheme: JIRA applications can generate email notifications for various events that happen throughout the lifecycle of an issue, including custom events. Notifications are defined within a notification scheme, which associates particular events with particular email recipients.
  3. Issue security Level: Issue security levels are created within issue security schemes and let you control which user or group of users can view an issue. If you try to open an issue to Atlassian support then you'll see they are using this resource.
    1. Here you can read more about it.
  4. A workflow scheme: You can use it to your issues types or projects, and you can change how they work. And you can reuse as you want. More information below: 
  5. An issue type scheme: An 'issue type scheme' defines a subset of issue types, which:
    1. restricts the set of available issue types for a project, and
    2. controls the order of available issue types and the default issue type shown to your users for a project.

      information The 'default issue type' is the issue type displayed in the selection-box when a user creates an issue.

      1. Read more here:
  6. an issue type screen scheme: An 'issue type screen scheme' associates a screen scheme (which defines mappings between screens and issue operations) with issue types. 
  7. a field configuration scheme: I do not know much more than this: JIRA applications let you add custom fields in addition to the built-in fields.
    1. But here - - you can read more.

I hope that I have helped you.

Best Regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

185 views 4 1
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