...
...
...
...
...
...
...
...
This section has use cases
...
that help you in understanding the usage of Validators provided by JMWE.
On this page:
Table of Contents |
---|
Linked Issue(s) validator
This validator can be used to ensure that issues linked to the current issue have certain characteristics
Sample use cases:
...
Prevent creation of more than 5 subtasks for a parent issue of "Story" issue type
...
Expand | ||
---|---|---|
| ||
|
...
|
...
|
...
|
...
|
Linked Issues Status validator
This validator can be used to ensure that the current issue's linked issues are in one of the selected statuses.
Sample use cases:
...
Block the transition of the Epic to Closed status, if its stories aren't closed.
...
Expand | ||
---|---|---|
| ||
|
Prevent creation of new subtasks to the parent if the parent is in "Resolved" or "Closed" or "Rejected" status
...
Expand | ||
---|---|---|
| ||
|
Build-your-own (scripted) Validator
This validator can be used to perform a validation with a Jira expression. Based on the result of the expression, the user is either allowed or blocked to transition to the destination status.
Sample use cases:
Force users to provide Fix Version/s only when the resolution is Fixed
...
Expand | ||
---|---|---|
| ||
|
...
Prevent the user from approving a hardware request if the respective hardware (count stored in a custom field) is out of stock
...
Expand | ||
---|---|---|
| ||
|
...
|
Prevent the employee from applying for a leave if the employee is in the 3 month probation period
...
Expand | ||
---|---|---|
| ||
|