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
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'
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
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
there is a ValueField in the workflow available which can be used to show/hide transitions based on issue types.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs