Use schemes to standardize company-managed spaces
5 min
Intermediate
By the end of this lesson, you’ll be able to:
- Describe the different types of schemes
- List the benefits of sharing schemes among company-managed spaces
What are schemes?
Schemes are collections of configurations associated with spaces that enable Jira admins to reuse configurations across multiple company-managed spaces. There are many types of schemes for different areas of a space.
👉 For example: Workflow schemes apply different workflows to different work types and spaces. A development team working in the DEV space has a workflow scheme. The scheme states that the workflow with a review should apply to bugs and stories, and the workflow without a review should apply to tasks and sub-tasks. The Jira admin can reuse this workflow scheme in other spaces.
👇 Here’s an example of the development team’s workflow scheme.
Team-managed spaces don’t have schemes and don’t use shared configurations.
Six schemes are always included in company-managed spaces:
- Work type scheme
- Permission scheme
- Notification scheme
- Field configuration scheme
- Workflow scheme
- Work type screen scheme
There is also an optional Work item security scheme. This scheme can be associated with a space to provide work item-level security.
👇Here are the work types included in company-managed spaces.
Several schemes can be configured per work type:
- A field configuration scheme consists of one or more field configurations, which can be configured per work type.
- A workflow scheme consists of one or more workflows, which can be configured per work type.
- A work type screen scheme consists of one or more screen schemes, which can be configured per work type. Those screen schemes consist of one or more screens. Screens like create, edit, and view can be configured per work item operation.
Only Jira admins can create and modify schemes and associate them with spaces.
Share schemes
If you use the same scheme for multiple spaces, any change to that scheme will impact all associated spaces. It’s important to consider the benefits and disadvantages of each before you start creating schemes.
👇 Click the tabs below to explore the benefits and disadvantages of shared and custom schemes.
Here are some benefits of sharing schemes:
- Easy to manage
- Reduces administrative overhead
- Apply changes to all spaces using the scheme
- User experience is more consistent and standardized
- Better system performance
- Jira won’t have to load as many features or screens when creating, editing, or closing work items
Here are some of the disadvantages of sharing schemes:
- Not as flexible
- Difficult to meet unique business requirements for different spaces
- Involve multiple stakeholders with every modification
Use as few schemes as possible and share them between similar spaces types or departments.
Let’s explore an example!
Naz is a Jira admin for a development team. One of the team’s business requirements is to set up each space similarly so that space members can perform the same types of tasks using scrum.
Here’s how Naz builds the space to meet the business requirement:
- First, Naz creates a new standard scrum software development space using DEV as the key.
- Next, he configures the space to create a standard set of schemes and configurations.
- He shares the standard space's configuration when creating the other scrum spaces.
- Finally, Naz applies the new schemes and configurations to in-progress scrum spaces.
How was this lesson?
next lesson
Map business requirements to Jira configurations
- Make sure Jira meets the needs of your users
- Discover and understand business requirements
- Map requirements to Jira configurations
- Implement Jira configurations