Versions Compared

Old Version 8

changes.mady.by.user Radhika Vijji.

Saved on

compared with

New Version 9

changes.mady.by.user Radhika Vijji.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Excerpt

A workflow validator that is based on the result of a Jira expression.  


If the Jira expression returns false, a validation error message will be displayed. This can be used to test or compare issue fields, to test linked issues, to check for open Sprints, etc.

To add the 'Build-your-own (scripted) Validator' to a transition:

  1. Click Edit for the workflow that has the transition you wish to configure the condition on.
  2. In the Workflow Designer, select the transition.
  3. Click on Validations in the properties panel.
  4. Click on Add validation.
  5. Select Build-your-own (scripted) Validator from the list of conditions.
  6. Click on Add to add the validator on the transition.
  7. Input a Jira expression in the Jira expression field.
  8. Input a message in the Error message field to display if the configured conditions are not satisfied.
  9. For information on how to write a 'Jira expression' see How to insert information using Jira expressions.
  10. Click on Add to add the condition to the transition.


Panel

Related links :

Refer to the Use cases for validators page for use cases for this validator.

For information on how to write a Jira expression, see How to insert information using Jira expressions.


When you add this validator to a transition and trigger the transition, the add-on checks the result of the Jira expression. If it returns true the validation will pass. If it returns false or any non-boolean value, a validation error message is displayed.

Note
titleAvoid Jira expressions errors

When a Jira expression throws an error, Jira considers the result as false and hence the workflow validator fails. The best way to avoid errors in your Jira expressions is to test your Jira expressions against an issue using the "Jira expression tester" before saving the validator. Here are typical problems you need to look out for:

  • Syntax errors: Currently, syntax errors are not logged in the JMWE logs when conditions and validators are run (because of a Jira bug). So you will never know why the validator failed if it's because of a syntax error. Testing the Jira expression, however, will show syntax errors.

  • null values: If your Jira expression returns null it is considered a non-boolean value and hence Jira returns an error. For example, to check that the issue is assigned, if you provide the Jira expression as:

    Code Block
    issue.assignee

    when tested against an issue that is unassigned the expression returns null. In such cases, the easiest is to use two logical not operators (!!) to return true if the issue is assigned ( !issue.assignee returns false hence !! issue.assignee will return true when the issue is assigned).

    Code Block
    !! issue.assignee

    You can also write a Jira expression to check that the result is not null like this:

    Code Block
    issue.assignee != null


  • If your Jira expression accesses properties of an object that is null, then your Jira expression and thereby your workflow validator fail with an error. For example, to check that the issue's parent is a Story if you provide the Jira expression:

    Code Block
    issue.parent.issuetype.name == "Story"

    when tested against an issue without a parent, the Jira expression will return an error "Type null does not have any properties". To handle this you should include an expression to test that the issue has a parent.

    Code Block
    !! issue.parent && issue.parent.issuetype.name == "Story"