From the course: Jira: Advanced Administration

Unlock the full course today

Join today to access over 24,500 courses taught by industry experts.

Sharing schemes between projects

Sharing schemes between projects - Jira Tutorial

From the course: Jira: Advanced Administration

Sharing schemes between projects

- Jira schemes exist so they can be shared between multiple projects. Instead of creating one scheme per project, I recommend one set of schemes per project type. Let's use issue types as an example. As I mentioned previously, I like to create one issue type scheme for dev type projects, one for support type projects, and another for task type projects. This way, there's a standard and each project type has a consistent set of issue types. Then, I make sure all the dev type projects use the dev issue type scheme. In this example, the dev and QA projects both use the scheme that contains epics, stories, bugs, tasks, and sub-tasks. It's really tempting to create new schemes, but when are they warranted? Before you create new schemes, make sure they're really needed to support a business case. For example, if you're creating a Jira project to collect requests from external users, that might require special settings or…

Contents