What is a workflow scheme?
Different types of work go through different processes. Jira enables teams to more accurately capture their workflows by associating different workflows with different issue types. Like a permission scheme, a workflow scheme refers to the set of associations between workflows and issue types. Every project requires at least one workflow scheme, and a workflow scheme can be applied to multiple projects.
Consider the following use case:
There is a single development team at an organization, and the development team uses a Jira project to manage its work. The project has unique workflows for each of its issue types:
- Bug issue type refers to an error that needs to be resolved, and uses statuses like “Triaged” and “Fixed”.
- Story issue type refers to feature-related work, and uses statuses like “Design WIP”, “Design Review”, and “Ready for Development”.
- Task and subtask issue types refer to all other types of project work, and use statuses like “To Do”, “In Progress” and “Done”.
Over the course of a year, the development team doubles in size. The engineering manager splits the team into two and creates a second Jira project. Since both teams have similar kinds of work, the first project’s workflow scheme, the set of associations between workflows and issue types, is applied to the second project.
With two teams owning their own projects, they can stay focused on relevant tasks and have the autonomy to manage their own work the way they see fit. At the same time, the engineering manager is able to get a complete and consistent view across all issues in both projects since they share the same workflow scheme.
Workflow schemes are currently available only in company-managed projects. Learn more
