Cloud Workflows is for any admin that wants to control who can do what and when in a workflow: The app brings new conditions and validators to Jira Cloud, empowering you to write your own custom workflows or use our pre-defined templates. Gain more fine-grained control of your workflows with the ease and convenience of the cloud.
Optimize down to the smallest detail: Cloud Workflows adds new conditions and validators to Jira Cloud. This allows you to link specific conditions to processes and thus automate your workflows even better. Using the templates provided, you can quickly set up your own conditions and validators. In addition, technically skilled admins can also define their own conditions and validators using Jira Expressions that let you count, aggregate, and compare any kind of information on a Jira issue. Comments, issue links, custom fields, the current project – no matter what, with Jira Expressions, you can create almost any kind of condition or validator.
Cloud Workflows extends Jira with maximum flexible conditions and validators based on Jira Expressions. With Cloud Workflows' custom condition/validator, admins can map almost any use case imaginable. Both the conditions and the validators come with a set of templates. These can be used immediately or customized individually.
Projects can be organized and secured more accurately – tailored to your and your team's specific needs.
You can enhance your own conditions and validators with Jira Expressions or choose from predefined templates.
Cloud Workflows makes all work steps on a project transparent. This helps you and your team to work more efficiently and to drive your goals forward.
Workflow conditions control whether a transition to move an issue from one state to the next is shown in the Jira UI. Use them to hide transitions that are not yet applicable or should be hidden.Get started quickly and choose from various pre-defined conditions within our condition editor or you can take your time and build your own custom conditions.
Workflow validators on the other hand control whether a transition is valid after a user chose it. While this sounds counter-intuitive, it makes a lot of sense when a transition screen is involved and the data entered on that screen needs to be checked.
Once again, you don’t need to start from scratch and can use pre-defined validators. Or start building your own Custom Validators – it’s totally up to you and your use case.
Cloud Workflows uses Jira Expressions, a language included in Jira Cloud that allows complex issues and conditions to be expressed very simply. This allows workflows in Jira to be designed even more flexibly. In Cloud Workflows, Jira Expressions are the basis for all conditions and validators. In addition, Jira Expressions can also be used to dynamically control the execution of Post Functions.
And of course, you'll want to make sure that your expression works the way you want it to. Cloud Workflows has got you covered here as it ships with a bundled version of Expression Tester, an app that lets all users try out Jira Expressions in a nice UI.
Once you have got Cloud Workflows installed, you'll notice a new entry in the Jira menu: "Jira Expressions". This new page in Jira allows you to test any Jira Expression right there in your browser!
Every Jira Expression is evaluated in a specific context that determines what kind of data can be used in the expression.
A user object, referring to the current user, will always be available, while other objects (such as project or issue) may or may not be available.
The Jira Expression Test page allows you to pick an issue and a project as additional context information. If you use a Jira Expression in a custom condition/validator, these two will always be available so you can test your expression under real-life conditions. To add a project or an issue simply enter the issue's or project's key into the corresponding issue fields.
Jira Expressions can be quite daunting. Don't worry, we got tons of examples in our Jira Expressions Cookbook.
Need help setting up your conditions and validators? We are happy to provide technical support to set up your conditions and validators according to your needs. Just let us know!
Want to know what custom conditions and validators can do for you and how they help simplify your daily work? Let’s have a look at the following use cases.
Use Case 1 – Processing of a task should only be possible in the current sprint:
Even in well-established agile teams, it can happen that not all specifications are always followed correctly. With Cloud Workflows for Jira, you can ensure directly in the app that all rules are adhered to. For example, only tasks that are assigned to the current sprint can be processed.
Solution: Set up a condition or validatorThis use case can be implemented as a condition or validator. In both cases, it is sufficient to set up a cloud workflow "custom validator" or a cloud workflow "custom condition" with the following Jira expression for the transition to the status "In progress":
Use Case 2 – No bug fix should be closed without an explanation:
Fixing bugs is good. Fixing bugs and explaining the bug in detail is even better. That way, it's easier not to repeat a bug. With Cloud Workflows, you can ensure that a developer writes a short explanatory comment before a bug can be closed.
Solution: Set up a validatorThis use case is best solved with a validator, as typically there is more information provided in the close screen of a bug. The following Jira Expression in the "close" transition of the bug ensures that the editor has provided a comment of at least 100 characters in length.
Say goodbye to Jira workflows you can’t work with or that do not cover your specific needs. With Cloud Workflows and Jira Expressions almost every imaginable workflow is possible – give it a try!