Workflow schemes are currently available only in company-managed projects. 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. 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. 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. The engineering manager splits the team into two and creates a second Jira Software project. Over the course of a year, the development team doubles in size.

Jira Service Management comes with templates intended to help IT and customer service teams handle their incoming requests. For example, Jira Software provides Scrum and Kanban templates for teams who work using Agile methodologies.

Task and subtask issue types refer to all other types of project work, and use statuses like “To Do”, “In Progress” and “Done”. Each Jira product comes with its own project templates.

Story issue type refers to feature-related work, and uses statuses like “Design WIP”, “Design Review”, and “Ready for Development”.

Bug issue type refers to an error that needs to be resolved, and uses statuses like “Triaged” and “Fixed”.

The project has unique workflows for each of its issue types: There is a single development team at an organization, and the development team uses a Jira Software project to manage its work.

Workfront for jira