Is it possible to use different workflows in a project, based on criteria other than the issue type

[Amir Katz (Outseer)]

I need to use different workflows in the same project, but deciding which workflow should be based on the issue type (supported) and on another field (standard or custom), e.g. Category.

Is this possible?

[Steve Thornhill · Accepted solution]

You can only have one workflow per issuetype. This is selected when you create a new issue (based on the issuetype) and before any of the fields have been entered.

You can have multiple routes through the workflow based on an customfield by using the conditions to enable/disable different statuses.

[Amir Katz (Outseer)]

Thanks, Steve, but this is the answer I did not want to hear :-(

Your suggestion is a acceptable workaround.

However, the problem with condition-based routing is that the conditions are not shown in the workflow diagram, so one has to read the textual definition of the workflow.

From a simple flow diagram, it becomes a computer code with conditions...

Alternatively, I might define a synthetic issue types, e.g.

• Type1-Category1
• Type1-Category2
• Type2-Category1,

etc.

It's a hack, but it will solve my problem.

[Steve Thornhill]

That's true.

As you are using Service Desk (assuming that from the tags) you already have the initial 2 choices on the customer portal - Request types, and then the actual issue type itself.