Conditions

A condition checks to make sure that a requirement has been met before you can see the next workflow transition. For example, you can add a ScriptRunner workflow condition that checks all subtasks have a set resolution before the parent task can be transitioned. Depending on what your organization requires, you may want to use workflow conditions provided by ScriptRunner. These conditions allow you to do more in your workflow, providing extra control or information. ScriptRunner includes built-in conditions that you can use right away, but you can also create your own Simple scripted condition. See below for a full list of our conditions: 

• All Sub-tasks Resolved Condition
• Checks if this Issue has Been in a Status Previously Condition
• Custom Script Condition
• Field(s) Required Condition
• Group(s) Condition
• JQL Query Matches Condition
• Linked Issues Condition
• Project Role(s) Condition
• Regular Expression Condition
• Simple Scripted Condition
• User(s) Condition
• User in Field(s) Condition