Is there a way to give each project their own workflow

[Sarge]

my company consists of several diverse project teams who themselves are building their own unique companies.  Right now we have just one workflow dictating the process for each team.  As a project manager that drives me a little crazy! Is there a way to give each project team their own workflow allowing them to determine their own process? Oh, and without driving my admins crazy.

[Fabian Lim · Accepted solution]

Hi @Dave Hall

Welcome to the community!

If your projects are Team Managed processes your team can set their own workflows themselves if they have project admin permissions.  Now, if you are using company based projects, you cannot have multiple workflows for projects and not drive the admins crazy.  The admins will hate you. 

Team managed projects vs company based projects: What are team-managed and company-managed projects? | Jira Software Cloud | Atlassian Support

You may want to consider workflows that are generic enough that can be applied to multiple projects.  By doing so, it becomes very helpful when you are doing Program/Portfolio reporting.  

Good Luck

[Sarge]

Thanks Fabian!

[Callum Carlile _Automation Consultants_]

Hi @Dave Hall , welcome to the community!

Issue types are mapped to workflows through Workflow Schemes, and workflow schemes are then associated to a project. So separate projects can use separate workflow schemes to have different workflows, and different issue types within the same project can also have different workflows.

In order to create a workflow, you will need to have Jira Admin permissions at a minimum, so there may be some work up front for your Jira admins if they're needing to create separate workflows, but any workflow created can be shared by other projects by using the same workflow scheme.

There's some more info about this here. I hope this helps!

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Yes, and it's actually by issue type as well as project!

If you are using a team-managed project, then the workflow(s) for it are accessed by going into the project settings and into each issue type.  The project will have started out with one workflow associated with all the issue types, but you can edit the workflow for each one individually.

With company managed projects, your administrators can create new workflows, then name them in a "workflow scheme" that they then tell the project to use.  This maps your issue types to workflows, so that you can do things like 

Project 1 bugs - use workflow A

Project 1 tasks - use workflow B

Project 2 bugs - use workflow C

Project 2 features - use workflow A

and so-on

[Mohamed Benziane]

Hi,

Welcome to the community.

If each project team have their own Jira project, yes they can have different workflow.

A workflow is tied to a issuetype define in the workflow scheme then the workflow scheme is associated to one or several project.

https://support.atlassian.com/jira-service-management-cloud/docs/overview-of-jira-cloud-workflows/

https://support.atlassian.com/jira-cloud-administration/docs/configure-workflow-schemes/