Conditional Workflow

[Ralf Müller]

Is it possible to define a transition of a workflow in such a way that it behaved differently for different issue types?

Example: I would like to define a field as mandatory for one issue type but as optional for another

[Henning Tietgens · Accepted solution]

You can use one workflow with different transitions for different issuetypes. Each transition has a condition which makes the condition only available if the issuetype is the right one. You can use the Script Runner plugin to create such a condition, e.g.

issue.issueTypeObject.name == 'Bug'

Henning

[Tarun Sapra]

You can use https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities/versions#b124

there is a ValueField in the workflow available which can be used to show/hide transitions based on issue types.

[Nic Brough -Adaptavist-]

You can associate different workflows with different issue types by project (e.g. in project A, bugs use workflow 1, features use workflow 2, and the rest use wokflow 3, but in project B, everything uses workflow 2)

However, that doesn't cover mandatory fields. Those are handled by "field configuration", which have the same level of flexibility

[Ralf Müller]

I would like to reuse one workflow...

[Nic Brough -Adaptavist-]

You can "reuse" as many workflows as you like, as much as you like. Workflow schemes simply tell Jira which workflows to use for which project/issuetype combinations

See https://confluence.atlassian.com/display/JIRA/Configuring+Workflow+Schemes