Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Use cases for validators

Owned by Radhika Vijji. (Unlicensed)
Last updated: Jun 30, 2020
4 min read

This section has use cases which help you in understand the usage of Validators provided by JMWE.

On this page:

Field has been modified validator

This validator can be used to block the user from progressing to a destination status unless a field has been modified.

Sample use cases:

 Validate the change in Resolution provided when closing an issue

  • Add the Field has been modified validator to the Close transition.

  • Select Resolution from Field.

 Validate that the Fix Version/s has been modified when the resolution is "Fixed"

  • Add the Field has been modified validator to the Close transition.

  • Select Fix Versions from Field.

  • Select the Conditional execution section

  • Input the following script: 

    issue.getAsString("resolution") == "Fixed"

Field is required validator

This validator can be used to ensure that a field has a value during a transition.

Sample use cases:

 Validate the Affects Version/s and Assignee fields for a non-empty value on creating a Bug.

  • Add the Field is required validator to the Create transition.

  • Select Affects Version/s and Assignee from Fields.

Comment required validator

This validator can be used to force the users to enter a comment while transitioning to destination status.

Sample use cases:

 Validate that a comment is entered when rejecting a Bug fix.

  • Add the Comment required validator to the Reject transition of the Bug workflow.

 Validate that a comment is entered when the resolution is "Won't Do"

  • Add the Comment required validator to the Done transition

  • Select the Conditional execution option

  • Input the following script: 

    issue.getAsString("resolution") == "Won't Do"

Field has single value validator

This validator can be used to check that a multi-valued field does not have more than one value during a transition.

Sample use cases:

 Validate the Fix Version/s for a single value on an issue when the issue is fixed.

 Validate that the Component/s field has only one value if the issue type is Story

Previous status validator

This validator can be used to stop the user from transitioning to a status unless the issue has previously been in a specified status in the workflow.

Sample use cases:

 Block the transition of an issue to Close status if it has not been approved.

Parent status validator

This validator can be used to stop the user from transitioning to a status unless the issue's parent has been in a selected status in the workflow.

Sample use cases:

 Block the trigger of "Start Progress" on subtasks until its parent is approved.


Scripted (Groovy) validator

This validator can be used to perform a validation with a groovy expression. Based on the result of the expression, the user is either allowed or blocked to transition to the destination status.

Sample use cases:

 Block the creation of a Bug if no Attachment is provided.

 Validate the Cascade select for values in parent and child select dropdowns

 Block the approving of the Change request if it has no confluence page linked

 Block the approval of an issue if there is no PDF attached either from before or added during the transition

This validator ensures that the current issue's related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.) are in one of the specified statuses.

Sample use cases:

 Block the transition of the Epic to Closed status, if its stories aren't closed.

This validator ensures that a link to one (or more) issue(s) from the current issue is being created during the transition, and/or that existing and/or newly related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.) have certain characteristics.

Sample use cases:

 Block the creation of a Bug, if it is not linked to the corresponding functionality requirement.