Field Required Validator
A workflow validator that ensures the specified field or fields have a value during a transition.
When this validator is added to a transition and that transition is triggered, the extension checks for a value in the selected field or fields. If no values are found, an error message is displayed; this error message will display a default value, or it can be customized.
On the Service Management portal view of a request, the customer will not see the Error message when the validator fails. This is due to a known limitation (JSDCLOUD-5853) with Atlassian.
Configure the validator
Follow the steps above to add a validator to a transition.
From the list of validators, select Field Required Validator (JMWE app).
The Field Required Validator page will open. Configure the validator as needed. See below for details on each of the configurations.
Click Add.
Please note: only 10 (ten) custom fields can be added to the selected fields for the Field Required validator; more than ten system fields can be added. If more than ten custom fields are added, it will not be possible to add the validator to the transition. This is a known issue with Jira expressions, as documented in ACJIRA-2312.
The following configurations are available:
Field(s) - Select the field or fields that are required for the issue to transition. Click the X beside a field to remove it from the list.
Error message - The error message that will display if the validator fails.
Validator scope
Conditional validation - Check this box to configure the validator to only run in specific circumstances.
Condition - Only visible when Conditional validation, above, is checked. Enter a Jira expression; if the expression evaluates to
true, the validator will run.Skip validation when cloning an issue - Check this option to skip the validator when an issue is being cloned.
Note: This validator does not work for the following fields:
Security Level
Watchers
Epic Color
Epic Name
Epic Status
Raised during
Additionally, it is not currently possible to verify the Parent field during a create transition, or if the Parent field is selected during a transition screen. This is due to a limitation in Atlassian’s implementation of the new Parent field (refer to https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/ for more information). The workaround for validating the Parent field is to create the Field Required validator using the epic-link (for Epic-Story relationships) or parent-link (for other relationships). This will still validate the Parent field, as currently some of the updates in Jira are cosmetic only.
Lastly, some custom fields from other apps, like Team of Jira Portfolio, though available in the list are not supported because of certain limitations (of the apps).
