Adding multiple workflows to a project

[Jonnie Wheeler]

I've been tring to add multiple workflows (12 in total) to a Kanban project but I'm unable to add more than one. Not sure what I'm doing wrong. 

[Trudy Claspill · Accepted solution]

Hello @Jonnie Wheeler 

Are you working with a Team Managed project or a Company Managed project? That information is at the bottom of the navigation panel on the left when you are viewing the project.

For a Company Managed project, you don't add workflows directly to the project. Instead you associate a Workflow Scheme to a project. A Workflow Scheme maps a Workflow to an Issue Type. You can have only one Workflow per Issue Type in a Workflow Scheme.

How many types of issues do you have in the project? If you don't have 12 or more issue types in that project, can you provide more information about how you are trying to use 12 different workflows in that one project?

Perhaps we are confused by the terminology you are using. Can you provide screen images to show us what you are trying to do?

[Jonnie Wheeler]

I'm working with a Company managed project that will have 12 issue types. From what I understand, I'll need to associate those 12 workflow schemes to the project. Is that correct? 

[Trudy Claspill]

No, that is not correct.

You associate only one Workflow Scheme to a project.

Within the Workflow Scheme you associate Workflows to Issue Types.

It is within the Workflow Scheme that you would add the 12 workflows and associate each workflow with the appropriate issue type.

Then you would associate the Workflow Scheme to the project.

https://support.atlassian.com/jira-cloud-administration/docs/create-and-manage-issue-workflows-and-issue-workflow-schemes/

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

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Do you have 12+ issue types set up?  And usable in that project?

[Jonnie Wheeler]

I haven't set up all 12 issues types because I was under the imprestion I needed 12 workflows for each issue type, but from what I understand, I'll need 12 workflow schemes that will need to be associated to the project.  

[Nic Brough -Adaptavist-]

No, I'm afraid that's not accurate.

You can only have one workflow per issue type, an issue type can never have more than one workflow.  But you can share workflows.

You need one workflow scheme, which has up to 13 lines saying "for this issue type, use workflow X". 

I've said 13 because you mention 12 workflows - because workflows are shared objects, you can associate more than one issue type with a workflow.  If you create a new workflow scheme, you will see it has a single line in it, saying "Default = workflow Y".

A project using that scheme will have 1 workflow, and all issue types in it will use workflow Y.

You add lines as exceptions to that, not forced mappings.  I would expect your workflow scheme to end up more like:

• Default: workflow X
• Bugs, Features, and defects: workflow Y
• Sub-tasks and technical-tasks: workflow Z

All 12 of your issue types are covered there, 2 on Z, 3 on Y, and the other 7 on X (and if you add more types, they'll automatically use X until you edit the scheme to say otherwise)